[web] Publish NG for f21
Petr Kovář
pmkovar at fedoraproject.org
Thu Jan 8 14:08:33 UTC 2015
commit 3407faa812c3da9fb13348977037f8f206b06bd7
Author: Petr Kovar <pkovar at redhat.com>
Date: Thu Jan 8 15:07:57 2015 +0100
Publish NG for f21
fedoradocs.db | Bin 1051648 -> 1054720 bytes
public_html/Sitemap | 24 +
public_html/as-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/as-IN/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/as-IN/opds-Fedora_Core.xml | 2 +-
public_html/as-IN/opds-Fedora_Documentation.xml | 2 +-
.../as-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/as-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/as-IN/opds.xml | 16 +-
public_html/as-IN/toc.html | 9 +
public_html/bg-BG/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bg-BG/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bg-BG/opds-Fedora_Core.xml | 2 +-
public_html/bg-BG/opds-Fedora_Documentation.xml | 2 +-
.../bg-BG/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bg-BG/opds-Fedora_Security_Team.xml | 2 +-
public_html/bg-BG/opds.xml | 16 +-
public_html/bg-BG/toc.html | 9 +
public_html/bn-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bn-IN/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bn-IN/opds-Fedora_Core.xml | 2 +-
public_html/bn-IN/opds-Fedora_Documentation.xml | 2 +-
.../bn-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bn-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/bn-IN/opds.xml | 16 +-
public_html/bn-IN/toc.html | 9 +
public_html/bs-BA/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bs-BA/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bs-BA/opds-Fedora_Core.xml | 2 +-
public_html/bs-BA/opds-Fedora_Documentation.xml | 2 +-
.../bs-BA/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bs-BA/opds-Fedora_Security_Team.xml | 2 +-
public_html/bs-BA/opds.xml | 16 +-
public_html/bs-BA/toc.html | 9 +
public_html/ca-ES/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ca-ES/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ca-ES/opds-Fedora_Core.xml | 2 +-
public_html/ca-ES/opds-Fedora_Documentation.xml | 2 +-
.../ca-ES/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ca-ES/opds-Fedora_Security_Team.xml | 2 +-
public_html/ca-ES/opds.xml | 16 +-
public_html/ca-ES/toc.html | 9 +
public_html/cs-CZ/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/cs-CZ/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/cs-CZ/opds-Fedora_Core.xml | 2 +-
public_html/cs-CZ/opds-Fedora_Documentation.xml | 2 +-
.../cs-CZ/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/cs-CZ/opds-Fedora_Security_Team.xml | 2 +-
public_html/cs-CZ/opds.xml | 16 +-
public_html/cs-CZ/toc.html | 9 +
public_html/da-DK/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/da-DK/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/da-DK/opds-Fedora_Core.xml | 2 +-
public_html/da-DK/opds-Fedora_Documentation.xml | 2 +-
.../da-DK/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/da-DK/opds-Fedora_Security_Team.xml | 2 +-
public_html/da-DK/opds.xml | 16 +-
public_html/da-DK/toc.html | 9 +
public_html/de-DE/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/de-DE/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/de-DE/opds-Fedora_Core.xml | 2 +-
public_html/de-DE/opds-Fedora_Documentation.xml | 2 +-
.../de-DE/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/de-DE/opds-Fedora_Security_Team.xml | 2 +-
public_html/de-DE/opds.xml | 16 +-
public_html/de-DE/toc.html | 9 +
public_html/el-GR/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/el-GR/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/el-GR/opds-Fedora_Core.xml | 2 +-
public_html/el-GR/opds-Fedora_Documentation.xml | 2 +-
.../el-GR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/el-GR/opds-Fedora_Security_Team.xml | 2 +-
public_html/el-GR/opds.xml | 16 +-
public_html/el-GR/toc.html | 9 +
.../Fedora-21-Networking_Guide-en-US.epub | Bin 0 -> 527968 bytes
.../Networking_Guide/Common_Content/css/common.css | 1528 +++++++
.../Common_Content/css/default.css | 3 +
.../Networking_Guide/Common_Content/css/lang.css | 2 +
.../Common_Content/css/overrides.css | 51 +
.../Networking_Guide/Common_Content/css/print.css | 16 +
.../Networking_Guide/Common_Content/images/1.png | Bin 0 -> 710 bytes
.../Networking_Guide/Common_Content/images/1.svg | 27 +
.../Networking_Guide/Common_Content/images/10.png | Bin 0 -> 985 bytes
.../Networking_Guide/Common_Content/images/10.svg | 31 +
.../Networking_Guide/Common_Content/images/11.png | Bin 0 -> 810 bytes
.../Networking_Guide/Common_Content/images/11.svg | 31 +
.../Networking_Guide/Common_Content/images/12.png | Bin 0 -> 1012 bytes
.../Networking_Guide/Common_Content/images/12.svg | 31 +
.../Networking_Guide/Common_Content/images/13.png | Bin 0 -> 1048 bytes
.../Networking_Guide/Common_Content/images/13.svg | 31 +
.../Networking_Guide/Common_Content/images/14.png | Bin 0 -> 914 bytes
.../Networking_Guide/Common_Content/images/14.svg | 31 +
.../Networking_Guide/Common_Content/images/15.png | Bin 0 -> 989 bytes
.../Networking_Guide/Common_Content/images/15.svg | 31 +
.../Networking_Guide/Common_Content/images/16.png | Bin 0 -> 1047 bytes
.../Networking_Guide/Common_Content/images/16.svg | 31 +
.../Networking_Guide/Common_Content/images/17.png | Bin 0 -> 888 bytes
.../Networking_Guide/Common_Content/images/17.svg | 31 +
.../Networking_Guide/Common_Content/images/18.png | Bin 0 -> 1075 bytes
.../Networking_Guide/Common_Content/images/18.svg | 31 +
.../Networking_Guide/Common_Content/images/19.png | Bin 0 -> 1049 bytes
.../Networking_Guide/Common_Content/images/19.svg | 31 +
.../Networking_Guide/Common_Content/images/2.png | Bin 0 -> 896 bytes
.../Networking_Guide/Common_Content/images/2.svg | 27 +
.../Networking_Guide/Common_Content/images/20.png | Bin 0 -> 1151 bytes
.../Networking_Guide/Common_Content/images/20.svg | 31 +
.../Networking_Guide/Common_Content/images/21.png | Bin 0 -> 994 bytes
.../Networking_Guide/Common_Content/images/21.svg | 31 +
.../Networking_Guide/Common_Content/images/22.png | Bin 0 -> 1162 bytes
.../Networking_Guide/Common_Content/images/22.svg | 31 +
.../Networking_Guide/Common_Content/images/23.png | Bin 0 -> 1207 bytes
.../Networking_Guide/Common_Content/images/23.svg | 31 +
.../Networking_Guide/Common_Content/images/24.png | Bin 0 -> 1081 bytes
.../Networking_Guide/Common_Content/images/24.svg | 31 +
.../Networking_Guide/Common_Content/images/25.png | Bin 0 -> 1173 bytes
.../Networking_Guide/Common_Content/images/25.svg | 31 +
.../Networking_Guide/Common_Content/images/26.png | Bin 0 -> 1208 bytes
.../Networking_Guide/Common_Content/images/26.svg | 31 +
.../Networking_Guide/Common_Content/images/27.png | Bin 0 -> 1080 bytes
.../Networking_Guide/Common_Content/images/27.svg | 31 +
.../Networking_Guide/Common_Content/images/28.png | Bin 0 -> 1225 bytes
.../Networking_Guide/Common_Content/images/28.svg | 31 +
.../Networking_Guide/Common_Content/images/29.png | Bin 0 -> 1196 bytes
.../Networking_Guide/Common_Content/images/29.svg | 31 +
.../Networking_Guide/Common_Content/images/3.png | Bin 0 -> 958 bytes
.../Networking_Guide/Common_Content/images/3.svg | 27 +
.../Networking_Guide/Common_Content/images/30.png | Bin 0 -> 1250 bytes
.../Networking_Guide/Common_Content/images/30.svg | 31 +
.../Networking_Guide/Common_Content/images/31.png | Bin 0 -> 1078 bytes
.../Networking_Guide/Common_Content/images/31.svg | 31 +
.../Networking_Guide/Common_Content/images/32.png | Bin 0 -> 1241 bytes
.../Networking_Guide/Common_Content/images/32.svg | 31 +
.../Networking_Guide/Common_Content/images/33.png | Bin 0 -> 1268 bytes
.../Networking_Guide/Common_Content/images/33.svg | 31 +
.../Networking_Guide/Common_Content/images/34.png | Bin 0 -> 1175 bytes
.../Networking_Guide/Common_Content/images/34.svg | 31 +
.../Networking_Guide/Common_Content/images/35.png | Bin 0 -> 1224 bytes
.../Networking_Guide/Common_Content/images/35.svg | 31 +
.../Networking_Guide/Common_Content/images/36.png | Bin 0 -> 1281 bytes
.../Networking_Guide/Common_Content/images/36.svg | 31 +
.../Networking_Guide/Common_Content/images/37.png | Bin 0 -> 1140 bytes
.../Networking_Guide/Common_Content/images/37.svg | 31 +
.../Networking_Guide/Common_Content/images/38.png | Bin 0 -> 1300 bytes
.../Networking_Guide/Common_Content/images/38.svg | 31 +
.../Networking_Guide/Common_Content/images/39.png | Bin 0 -> 1294 bytes
.../Networking_Guide/Common_Content/images/39.svg | 31 +
.../Networking_Guide/Common_Content/images/4.png | Bin 0 -> 849 bytes
.../Networking_Guide/Common_Content/images/4.svg | 27 +
.../Networking_Guide/Common_Content/images/40.png | Bin 0 -> 1130 bytes
.../Networking_Guide/Common_Content/images/40.svg | 31 +
.../Networking_Guide/Common_Content/images/5.png | Bin 0 -> 900 bytes
.../Networking_Guide/Common_Content/images/5.svg | 27 +
.../Networking_Guide/Common_Content/images/6.png | Bin 0 -> 929 bytes
.../Networking_Guide/Common_Content/images/6.svg | 27 +
.../Networking_Guide/Common_Content/images/7.png | Bin 0 -> 807 bytes
.../Networking_Guide/Common_Content/images/7.svg | 27 +
.../Networking_Guide/Common_Content/images/8.png | Bin 0 -> 962 bytes
.../Networking_Guide/Common_Content/images/8.svg | 27 +
.../Networking_Guide/Common_Content/images/9.png | Bin 0 -> 936 bytes
.../Networking_Guide/Common_Content/images/9.svg | 27 +
.../Common_Content/images/bkgrnd_greydots.png | Bin 0 -> 157 bytes
.../Common_Content/images/bullet_arrowblue.png | Bin 0 -> 177 bytes
.../Common_Content/images/documentation.png | Bin 0 -> 623 bytes
.../Networking_Guide/Common_Content/images/dot.png | Bin 0 -> 98 bytes
.../Common_Content/images/dot2.png | Bin 0 -> 98 bytes
.../Common_Content/images/green.png | Bin 0 -> 176 bytes
.../Common_Content/images/h1-bg.png | Bin 0 -> 565 bytes
.../Common_Content/images/image_left.png | Bin 0 -> 1114 bytes
.../Common_Content/images/image_right.png | Bin 0 -> 2260 bytes
.../Common_Content/images/important.png | Bin 0 -> 2080 bytes
.../Common_Content/images/important.svg | 106 +
.../Common_Content/images/logo.png | Bin 0 -> 1114 bytes
.../Common_Content/images/note.png | Bin 0 -> 1241 bytes
.../Common_Content/images/note.svg | 111 +
.../Networking_Guide/Common_Content/images/red.png | Bin 0 -> 163 bytes
.../Common_Content/images/shade.png | Bin 0 -> 101 bytes
.../Common_Content/images/shine.png | Bin 0 -> 146 bytes
.../Common_Content/images/stock-go-back.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-forward.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-up.png | Bin 0 -> 760 bytes
.../Common_Content/images/stock-home.png | Bin 0 -> 808 bytes
.../Common_Content/images/title_logo.png | Bin 0 -> 13399 bytes
.../Common_Content/images/title_logo.svg | 61 +
.../Common_Content/images/warning.png | Bin 0 -> 1340 bytes
.../Common_Content/images/warning.svg | 89 +
.../Common_Content/images/watermark-draft.png | Bin 0 -> 25365 bytes
.../Common_Content/images/yellow.png | Bin 0 -> 175 bytes
.../images/Editing-Bridge-Connection-1_Gnome3.png | Bin 0 -> 33443 bytes
.../images/Network-Details-Wired_Gnome3.png | Bin 0 -> 47589 bytes
.../images/Network-Wired_Gnome3.png | Bin 0 -> 55844 bytes
.../21/html-single/Networking_Guide/index.html | 4752 ++++++++++++++++++++
.../Networking_Guide/Common_Content/css/common.css | 1528 +++++++
.../Common_Content/css/default.css | 3 +
.../Networking_Guide/Common_Content/css/lang.css | 2 +
.../Common_Content/css/overrides.css | 51 +
.../Networking_Guide/Common_Content/css/print.css | 16 +
.../Networking_Guide/Common_Content/images/1.png | Bin 0 -> 710 bytes
.../Networking_Guide/Common_Content/images/1.svg | 27 +
.../Networking_Guide/Common_Content/images/10.png | Bin 0 -> 985 bytes
.../Networking_Guide/Common_Content/images/10.svg | 31 +
.../Networking_Guide/Common_Content/images/11.png | Bin 0 -> 810 bytes
.../Networking_Guide/Common_Content/images/11.svg | 31 +
.../Networking_Guide/Common_Content/images/12.png | Bin 0 -> 1012 bytes
.../Networking_Guide/Common_Content/images/12.svg | 31 +
.../Networking_Guide/Common_Content/images/13.png | Bin 0 -> 1048 bytes
.../Networking_Guide/Common_Content/images/13.svg | 31 +
.../Networking_Guide/Common_Content/images/14.png | Bin 0 -> 914 bytes
.../Networking_Guide/Common_Content/images/14.svg | 31 +
.../Networking_Guide/Common_Content/images/15.png | Bin 0 -> 989 bytes
.../Networking_Guide/Common_Content/images/15.svg | 31 +
.../Networking_Guide/Common_Content/images/16.png | Bin 0 -> 1047 bytes
.../Networking_Guide/Common_Content/images/16.svg | 31 +
.../Networking_Guide/Common_Content/images/17.png | Bin 0 -> 888 bytes
.../Networking_Guide/Common_Content/images/17.svg | 31 +
.../Networking_Guide/Common_Content/images/18.png | Bin 0 -> 1075 bytes
.../Networking_Guide/Common_Content/images/18.svg | 31 +
.../Networking_Guide/Common_Content/images/19.png | Bin 0 -> 1049 bytes
.../Networking_Guide/Common_Content/images/19.svg | 31 +
.../Networking_Guide/Common_Content/images/2.png | Bin 0 -> 896 bytes
.../Networking_Guide/Common_Content/images/2.svg | 27 +
.../Networking_Guide/Common_Content/images/20.png | Bin 0 -> 1151 bytes
.../Networking_Guide/Common_Content/images/20.svg | 31 +
.../Networking_Guide/Common_Content/images/21.png | Bin 0 -> 994 bytes
.../Networking_Guide/Common_Content/images/21.svg | 31 +
.../Networking_Guide/Common_Content/images/22.png | Bin 0 -> 1162 bytes
.../Networking_Guide/Common_Content/images/22.svg | 31 +
.../Networking_Guide/Common_Content/images/23.png | Bin 0 -> 1207 bytes
.../Networking_Guide/Common_Content/images/23.svg | 31 +
.../Networking_Guide/Common_Content/images/24.png | Bin 0 -> 1081 bytes
.../Networking_Guide/Common_Content/images/24.svg | 31 +
.../Networking_Guide/Common_Content/images/25.png | Bin 0 -> 1173 bytes
.../Networking_Guide/Common_Content/images/25.svg | 31 +
.../Networking_Guide/Common_Content/images/26.png | Bin 0 -> 1208 bytes
.../Networking_Guide/Common_Content/images/26.svg | 31 +
.../Networking_Guide/Common_Content/images/27.png | Bin 0 -> 1080 bytes
.../Networking_Guide/Common_Content/images/27.svg | 31 +
.../Networking_Guide/Common_Content/images/28.png | Bin 0 -> 1225 bytes
.../Networking_Guide/Common_Content/images/28.svg | 31 +
.../Networking_Guide/Common_Content/images/29.png | Bin 0 -> 1196 bytes
.../Networking_Guide/Common_Content/images/29.svg | 31 +
.../Networking_Guide/Common_Content/images/3.png | Bin 0 -> 958 bytes
.../Networking_Guide/Common_Content/images/3.svg | 27 +
.../Networking_Guide/Common_Content/images/30.png | Bin 0 -> 1250 bytes
.../Networking_Guide/Common_Content/images/30.svg | 31 +
.../Networking_Guide/Common_Content/images/31.png | Bin 0 -> 1078 bytes
.../Networking_Guide/Common_Content/images/31.svg | 31 +
.../Networking_Guide/Common_Content/images/32.png | Bin 0 -> 1241 bytes
.../Networking_Guide/Common_Content/images/32.svg | 31 +
.../Networking_Guide/Common_Content/images/33.png | Bin 0 -> 1268 bytes
.../Networking_Guide/Common_Content/images/33.svg | 31 +
.../Networking_Guide/Common_Content/images/34.png | Bin 0 -> 1175 bytes
.../Networking_Guide/Common_Content/images/34.svg | 31 +
.../Networking_Guide/Common_Content/images/35.png | Bin 0 -> 1224 bytes
.../Networking_Guide/Common_Content/images/35.svg | 31 +
.../Networking_Guide/Common_Content/images/36.png | Bin 0 -> 1281 bytes
.../Networking_Guide/Common_Content/images/36.svg | 31 +
.../Networking_Guide/Common_Content/images/37.png | Bin 0 -> 1140 bytes
.../Networking_Guide/Common_Content/images/37.svg | 31 +
.../Networking_Guide/Common_Content/images/38.png | Bin 0 -> 1300 bytes
.../Networking_Guide/Common_Content/images/38.svg | 31 +
.../Networking_Guide/Common_Content/images/39.png | Bin 0 -> 1294 bytes
.../Networking_Guide/Common_Content/images/39.svg | 31 +
.../Networking_Guide/Common_Content/images/4.png | Bin 0 -> 849 bytes
.../Networking_Guide/Common_Content/images/4.svg | 27 +
.../Networking_Guide/Common_Content/images/40.png | Bin 0 -> 1130 bytes
.../Networking_Guide/Common_Content/images/40.svg | 31 +
.../Networking_Guide/Common_Content/images/5.png | Bin 0 -> 900 bytes
.../Networking_Guide/Common_Content/images/5.svg | 27 +
.../Networking_Guide/Common_Content/images/6.png | Bin 0 -> 929 bytes
.../Networking_Guide/Common_Content/images/6.svg | 27 +
.../Networking_Guide/Common_Content/images/7.png | Bin 0 -> 807 bytes
.../Networking_Guide/Common_Content/images/7.svg | 27 +
.../Networking_Guide/Common_Content/images/8.png | Bin 0 -> 962 bytes
.../Networking_Guide/Common_Content/images/8.svg | 27 +
.../Networking_Guide/Common_Content/images/9.png | Bin 0 -> 936 bytes
.../Networking_Guide/Common_Content/images/9.svg | 27 +
.../Common_Content/images/bkgrnd_greydots.png | Bin 0 -> 157 bytes
.../Common_Content/images/bullet_arrowblue.png | Bin 0 -> 177 bytes
.../Common_Content/images/documentation.png | Bin 0 -> 623 bytes
.../Networking_Guide/Common_Content/images/dot.png | Bin 0 -> 98 bytes
.../Common_Content/images/dot2.png | Bin 0 -> 98 bytes
.../Common_Content/images/green.png | Bin 0 -> 176 bytes
.../Common_Content/images/h1-bg.png | Bin 0 -> 565 bytes
.../Common_Content/images/image_left.png | Bin 0 -> 1114 bytes
.../Common_Content/images/image_right.png | Bin 0 -> 2260 bytes
.../Common_Content/images/important.png | Bin 0 -> 2080 bytes
.../Common_Content/images/important.svg | 106 +
.../Common_Content/images/logo.png | Bin 0 -> 1114 bytes
.../Common_Content/images/note.png | Bin 0 -> 1241 bytes
.../Common_Content/images/note.svg | 111 +
.../Networking_Guide/Common_Content/images/red.png | Bin 0 -> 163 bytes
.../Common_Content/images/shade.png | Bin 0 -> 101 bytes
.../Common_Content/images/shine.png | Bin 0 -> 146 bytes
.../Common_Content/images/stock-go-back.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-forward.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-up.png | Bin 0 -> 760 bytes
.../Common_Content/images/stock-home.png | Bin 0 -> 808 bytes
.../Common_Content/images/title_logo.png | Bin 0 -> 13399 bytes
.../Common_Content/images/title_logo.svg | 61 +
.../Common_Content/images/warning.png | Bin 0 -> 1340 bytes
.../Common_Content/images/warning.svg | 89 +
.../Common_Content/images/watermark-draft.png | Bin 0 -> 25365 bytes
.../Common_Content/images/yellow.png | Bin 0 -> 175 bytes
.../Networking_Guide/app-Revision_History.html | 21 +
.../ch-Configure_802_1Q_VLAN_Tagging.html | 25 +
.../Networking_Guide/ch-Configure_Host_Names.html | 21 +
.../ch-Configure_Network_Bonding.html | 32 +
.../ch-Configure_Network_Bridging.html | 91 +
.../ch-Configure_Network_Teaming.html | 19 +
.../Networking_Guide/ch-Configure_Networking.html | 31 +
.../ch-Consistent_Network_Device_Naming.html | 30 +
.../21/html/Networking_Guide/ch-DHCP_Servers.html | 17 +
.../21/html/Networking_Guide/ch-DNS_Servers.html | 41 +
.../ch-Introduction_to_Fedora_Networking.html | 15 +
.../21/html/Networking_Guide/ch09s02s03.html | 47 +
.../21/html/Networking_Guide/dhcp-relay-agent.html | 29 +
.../images/Editing-Bridge-Connection-1_Gnome3.png | Bin 0 -> 33443 bytes
.../images/Network-Details-Wired_Gnome3.png | Bin 0 -> 47589 bytes
.../images/Network-Wired_Gnome3.png | Bin 0 -> 55844 bytes
.../Fedora/21/html/Networking_Guide/index.html | 36 +
.../Fedora/21/html/Networking_Guide/ix01.html | 9 +
.../21/html/Networking_Guide/lease-database.html | 17 +
.../21/html/Networking_Guide/part-Networking.html | 11 +
.../21/html/Networking_Guide/part-Servers.html | 11 +
.../Fedora/21/html/Networking_Guide/pr01.html | 21 +
.../Fedora/21/html/Networking_Guide/pr01s05.html | 61 +
.../21/html/Networking_Guide/pr01s05s02.html | 34 +
.../21/html/Networking_Guide/pr01s05s03.html | 17 +
.../Networking_Guide/pref-Acknowledgments.html | 11 +
.../sec-Activating_a_Channel_Bond.html | 36 +
...Add_a_port_to_a_Network_Team_Using_iputils.html | 14 +
...an_address_to_a_Network_Team_Using_iputils.html | 13 +
..._Configuration_to_a_Port_in_a_Network_Team.html | 21 +
.../Fedora/21/html/Networking_Guide/sec-BIND.html | 15 +
..._interface_to_a_Network_Team_Using_iputils.html | 13 +
...c-Comparison_of_Network_Teaming_to_Bonding.html | 177 +
...e_802_1Q_VLAN_Tagging-additional_resources.html | 19 +
...-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html | 67 +
...802_1Q_VLAN_Tagging_Using_the_Command_Line.html | 33 +
..._Tagging_Using_the_Command_Line_Tool_nmcli.html | 119 +
...-Configure_802_1Q_VLAN_Tagging_ip_Commands.html | 24 +
...t_Selectors_for_Hash_Computation_Algorithm.html | 37 +
...sec-Configure_Monitoring_of_the_Link_State.html | 106 +
...igure_Network_Bonding-additional_resources.html | 17 +
...igure_Network_Bonding_Online_Documentation.html | 13 +
.../sec-Configure_Network_Teaming_Using_nmcli.html | 77 +
...-Configure_Networking-additional_resources.html | 19 +
...-Configure_Networking_Online_Documentation.html | 17 +
.../sec-Configure_Port_Selection_Override.html | 22 +
...gure_a_Network_Team_Using-the_Command_Line.html | 113 +
...Configure_dhcrelay_as_a_DHCPv6_relay_agent.html | 19 +
.../sec-Configure_teamd_Runners.html | 22 +
.../sec-Configure_the_LACP_Runner.html | 31 +
.../sec-Configure_the_activebackup_Runner.html | 82 +
.../sec-Configure_the_loadbalance_Runner.html | 40 +
.../sec-Configure_the_random_Runner.html | 22 +
.../sec-Configure_the_roundrobin_Runner.html | 20 +
.../sec-Configuring_Connection_Settings.html | 206 +
.../sec-Configuring_Host_Names_Using_nmcli.html | 19 +
...uring_IPv6_Tokenized_Interface_Identifiers.html | 37 +
...uring_New_and_Editing_Existing_Connections.html | 33 +
...Configuring_Options_of_a_Team_Using_teamnl.html | 15 +
.../sec-Configuring_Static_Routes_Using_nmcli.html | 31 +
...c-Configuring_Static_Routes_in_ifcfg_files.html | 46 +
.../sec-Configuring_a_Multihomed_DHCP_Server.html | 110 +
...ring_a_Network_Interface_Using_ip_commands.html | 37 +
.../sec-Configuring_a_Wi-Fi_Connection.html | 71 +
...ec-Configuring_a_Wired_Ethernet_Connection.html | 47 +
.../sec-Connecting_to_a_Network_Automatically.html | 21 +
.../sec-Connecting_to_a_Network_Using_nmcli.html | 197 +
...twork_Device_Naming-Enabling_and_Disabling.html | 17 +
...sec-Consistent_Network_Device_Naming-Notes.html | 13 +
...Network_Device_Naming-additional_resources.html | 17 +
...nt_Network_Device_Naming_Using_biosdevname.html | 47 +
.../sec-Controlling_teamd_with_teamdctl.html | 29 +
...ling_the_Selection_of_Network_Device_Names.html | 17 +
.../sec-Converting_a_Bond_to_a_Team.html | 34 +
.../sec-Create_a_Channel_Bonding_Interface.html | 31 +
.../sec-Create_a_Network_Bridge.html | 85 +
.../sec-Creating_Multiple_Bonds.html | 34 +
.../sec-Creating_SLAVE_Interfaces.html | 21 +
...sec-Creating_a_Bond_Connection_Using_a_GUI.html | 101 +
.../sec-Creating_a_Network_Team_Using_a_GUI.html | 71 +
...-Creating_a_Network_Team_Using_ifcfg_Files.html | 35 +
...Disabling_Consistent_Network_Device_Naming.html | 24 +
.../sec-Establishing_a_DSL_Connection.html | 59 +
...Establishing_a_Mobile_Broadband_Connection.html | 107 +
.../sec-Establishing_a_VPN_Connection.html | 81 +
.../sec-Install_the_Network_Teaming_Daemon.html | 13 +
.../sec-Installing_NetworkManager.html | 24 +
.../sec-Interacting_with_NetworkManager.html | 24 +
..._to_Fedora_Networking-additional_resources.html | 19 +
.../sec-Introduction_to_NetworkManager.html | 37 +
...c-Listing_the_ports_of_a_Team_Using_teamnl.html | 15 +
...rk_Devices_Available_for_Linux_on_System_z.html | 29 +
.../sec-Naming_Scheme_for_VLAN_Interfaces.html | 21 +
...sec-NetworkManager_and_the_Network_Scripts.html | 42 +
...k_Bonding_Using_the_Command_Line_Interface.html | 19 +
...the_NetworkManager_Command_Line_Tool_nmcli.html | 32 +
.../sec-Network_Bridging-additional_resources.html | 17 +
..._Bridging_Using_the_Command_Line_Interface.html | 16 +
...the_NetworkManager_Command_Line_Tool_nmcli.html | 54 +
.../sec-Network_Config_Using_CLI.html | 19 +
.../sec-Network_Config_Using_nmcli.html | 14 +
...etwork_Configuration_Using_sysconfig_Files.html | 43 +
.../sec-Network_Teaming-additional_resources.html | 21 +
.../sec-Preface-About_this_book.html | 11 +
.../sec-Preface-Book_Organization.html | 39 +
.../Networking_Guide/sec-Preface-Feedback.html | 19 +
.../sec-Remove_a_Port_From_a_Network_Team.html | 13 +
...terfaces_to_Use_as_Port_for_a_Network_Team.html | 21 +
...lecting_Network_Team_Configuration_Methods.html | 17 +
...ng_the_Active_Ports_of_a_Team_Using_teamnl.html | 16 +
.../sec-Static-Routes_and_the_Default_Gateway.html | 39 +
...ystem-wide_and_Private_Connection_Profiles.html | 37 +
...lt_Behavior_of_Master_and_Slave_Interfaces.html | 28 +
...nderstanding_the_Device_Renaming_Procedure.html | 21 +
...the_Network_Teaming_Daemon_and_the_Runners.html | 35 +
...Predictable_Network_Interface_Device_Names.html | 54 +
.../sec-Using_Channel_Bonding.html | 202 +
...er_with_the_GNOME_Graphical_User_Interface.html | 15 +
.../sec-Using_the_Command_Line_Interface.html | 38 +
...the_NetworkManager_Command_Line_Tool_nmcli.html | 86 +
..._Configuration_of_a_Port_in_a_Network_Team.html | 13 +
...ng_the_Active_Ports_of_a_Team_Using_teamnl.html | 14 +
.../21/html/Networking_Guide/sec-Whats-New.html | 17 +
.../Networking_Guide/sec-additional_resources.html | 25 +
.../sec-bind-additional-resources.html | 33 +
.../21/html/Networking_Guide/sec-bind-dig.html | 96 +
.../html/Networking_Guide/sec-bind-features.html | 35 +
.../html/Networking_Guide/sec-bind-mistakes.html | 21 +
.../html/Networking_Guide/sec-bind-namedconf.html | 405 ++
.../21/html/Networking_Guide/sec-bind-rndc.html | 88 +
.../21/html/Networking_Guide/sec-bind-zone.html | 255 ++
.../sec-dhcp-additional-resources.html | 25 +
.../sec-dhcp-configuring-server.html | 112 +
.../Networking_Guide/sec-dhcp_for_ipv6_dhcpv6.html | 24 +
.../sec-hostnamectl-Online_Documentation.html | 11 +
.../Networking_Guide/sec-teamd_docs-online.html | 16 +
.../sec_Changing_Host_Names_Remotely.html | 13 +
.../sec_Clear_a_Particular_Host_Name.html | 13 +
...c_Configuring_Host_Names_Using_hostnamectl.html | 15 +
.../sec_Set_All_the_Host_Names.html | 13 +
.../sec_Set_a_Particular_Host_Name.html | 19 +
.../sec_Troubleshooting_Network_Device_Naming.html | 33 +
.../Fedora-21-Networking_Guide-en-US.pdf | Bin 0 -> 1221611 bytes
public_html/en-US/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/en-US/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/en-US/opds-Fedora_Core.xml | 2 +-
public_html/en-US/opds-Fedora_Documentation.xml | 2 +-
.../en-US/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/en-US/opds-Fedora_Security_Team.xml | 2 +-
public_html/en-US/opds.xml | 16 +-
public_html/en-US/toc.html | 9 +
public_html/es-ES/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/es-ES/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/es-ES/opds-Fedora_Core.xml | 2 +-
public_html/es-ES/opds-Fedora_Documentation.xml | 2 +-
.../es-ES/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/es-ES/opds-Fedora_Security_Team.xml | 2 +-
public_html/es-ES/opds.xml | 16 +-
public_html/es-ES/toc.html | 9 +
public_html/fa-IR/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fa-IR/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fa-IR/opds-Fedora_Core.xml | 2 +-
public_html/fa-IR/opds-Fedora_Documentation.xml | 2 +-
.../fa-IR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fa-IR/opds-Fedora_Security_Team.xml | 2 +-
public_html/fa-IR/opds.xml | 16 +-
public_html/fa-IR/toc.html | 9 +
public_html/fi-FI/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fi-FI/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fi-FI/opds-Fedora_Core.xml | 2 +-
public_html/fi-FI/opds-Fedora_Documentation.xml | 2 +-
.../fi-FI/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fi-FI/opds-Fedora_Security_Team.xml | 2 +-
public_html/fi-FI/opds.xml | 16 +-
public_html/fi-FI/toc.html | 9 +
public_html/fr-FR/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fr-FR/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fr-FR/opds-Fedora_Core.xml | 2 +-
public_html/fr-FR/opds-Fedora_Documentation.xml | 2 +-
.../fr-FR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fr-FR/opds-Fedora_Security_Team.xml | 2 +-
public_html/fr-FR/opds.xml | 16 +-
public_html/fr-FR/toc.html | 9 +
public_html/gu-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/gu-IN/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/gu-IN/opds-Fedora_Core.xml | 2 +-
public_html/gu-IN/opds-Fedora_Documentation.xml | 2 +-
.../gu-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/gu-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/gu-IN/opds.xml | 16 +-
public_html/gu-IN/toc.html | 9 +
public_html/he-IL/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/he-IL/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/he-IL/opds-Fedora_Core.xml | 2 +-
public_html/he-IL/opds-Fedora_Documentation.xml | 2 +-
.../he-IL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/he-IL/opds-Fedora_Security_Team.xml | 2 +-
public_html/he-IL/opds.xml | 16 +-
public_html/he-IL/toc.html | 9 +
public_html/hi-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/hi-IN/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/hi-IN/opds-Fedora_Core.xml | 2 +-
public_html/hi-IN/opds-Fedora_Documentation.xml | 2 +-
.../hi-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/hi-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/hi-IN/opds.xml | 16 +-
public_html/hi-IN/toc.html | 9 +
public_html/hu-HU/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/hu-HU/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/hu-HU/opds-Fedora_Core.xml | 2 +-
public_html/hu-HU/opds-Fedora_Documentation.xml | 2 +-
.../hu-HU/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/hu-HU/opds-Fedora_Security_Team.xml | 2 +-
public_html/hu-HU/opds.xml | 16 +-
public_html/hu-HU/toc.html | 9 +
public_html/ia/Site_Statistics.html | 4 +-
.../ia/opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ia/opds-Fedora.xml | 20 +-
.../ia/opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ia/opds-Fedora_Core.xml | 2 +-
public_html/ia/opds-Fedora_Documentation.xml | 2 +-
public_html/ia/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ia/opds-Fedora_Security_Team.xml | 2 +-
public_html/ia/opds.xml | 16 +-
public_html/ia/toc.html | 9 +
public_html/id-ID/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/id-ID/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/id-ID/opds-Fedora_Core.xml | 2 +-
public_html/id-ID/opds-Fedora_Documentation.xml | 2 +-
.../id-ID/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/id-ID/opds-Fedora_Security_Team.xml | 2 +-
public_html/id-ID/opds.xml | 16 +-
public_html/id-ID/toc.html | 9 +
public_html/index.html | 2 +-
public_html/it-IT/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/it-IT/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/it-IT/opds-Fedora_Core.xml | 2 +-
public_html/it-IT/opds-Fedora_Documentation.xml | 2 +-
.../it-IT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/it-IT/opds-Fedora_Security_Team.xml | 2 +-
public_html/it-IT/opds.xml | 16 +-
public_html/it-IT/toc.html | 9 +
public_html/ja-JP/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ja-JP/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ja-JP/opds-Fedora_Core.xml | 2 +-
public_html/ja-JP/opds-Fedora_Documentation.xml | 2 +-
.../ja-JP/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ja-JP/opds-Fedora_Security_Team.xml | 2 +-
public_html/ja-JP/opds.xml | 16 +-
public_html/ja-JP/toc.html | 9 +
public_html/kn-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/kn-IN/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/kn-IN/opds-Fedora_Core.xml | 2 +-
public_html/kn-IN/opds-Fedora_Documentation.xml | 2 +-
.../kn-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/kn-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/kn-IN/opds.xml | 16 +-
public_html/kn-IN/toc.html | 9 +
public_html/ko-KR/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ko-KR/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ko-KR/opds-Fedora_Core.xml | 2 +-
public_html/ko-KR/opds-Fedora_Documentation.xml | 2 +-
.../ko-KR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ko-KR/opds-Fedora_Security_Team.xml | 2 +-
public_html/ko-KR/opds.xml | 16 +-
public_html/ko-KR/toc.html | 9 +
public_html/lt-LT/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/lt-LT/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/lt-LT/opds-Fedora_Core.xml | 2 +-
public_html/lt-LT/opds-Fedora_Documentation.xml | 2 +-
.../lt-LT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/lt-LT/opds-Fedora_Security_Team.xml | 2 +-
public_html/lt-LT/opds.xml | 16 +-
public_html/lt-LT/toc.html | 9 +
public_html/ml-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ml-IN/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ml-IN/opds-Fedora_Core.xml | 2 +-
public_html/ml-IN/opds-Fedora_Documentation.xml | 2 +-
.../ml-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ml-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/ml-IN/opds.xml | 16 +-
public_html/ml-IN/toc.html | 9 +
public_html/mr-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/mr-IN/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/mr-IN/opds-Fedora_Core.xml | 2 +-
public_html/mr-IN/opds-Fedora_Documentation.xml | 2 +-
.../mr-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/mr-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/mr-IN/opds.xml | 16 +-
public_html/mr-IN/toc.html | 9 +
public_html/nb-NO/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/nb-NO/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/nb-NO/opds-Fedora_Core.xml | 2 +-
public_html/nb-NO/opds-Fedora_Documentation.xml | 2 +-
.../nb-NO/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/nb-NO/opds-Fedora_Security_Team.xml | 2 +-
public_html/nb-NO/opds.xml | 16 +-
public_html/nb-NO/toc.html | 9 +
public_html/nl-NL/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/nl-NL/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/nl-NL/opds-Fedora_Core.xml | 2 +-
public_html/nl-NL/opds-Fedora_Documentation.xml | 2 +-
.../nl-NL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/nl-NL/opds-Fedora_Security_Team.xml | 2 +-
public_html/nl-NL/opds.xml | 16 +-
public_html/nl-NL/toc.html | 9 +
public_html/opds.xml | 92 +-
public_html/or-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/or-IN/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/or-IN/opds-Fedora_Core.xml | 2 +-
public_html/or-IN/opds-Fedora_Documentation.xml | 2 +-
.../or-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/or-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/or-IN/opds.xml | 16 +-
public_html/or-IN/toc.html | 9 +
public_html/pa-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pa-IN/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pa-IN/opds-Fedora_Core.xml | 2 +-
public_html/pa-IN/opds-Fedora_Documentation.xml | 2 +-
.../pa-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pa-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/pa-IN/opds.xml | 16 +-
public_html/pa-IN/toc.html | 9 +
public_html/pl-PL/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pl-PL/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pl-PL/opds-Fedora_Core.xml | 2 +-
public_html/pl-PL/opds-Fedora_Documentation.xml | 2 +-
.../pl-PL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pl-PL/opds-Fedora_Security_Team.xml | 2 +-
public_html/pl-PL/opds.xml | 16 +-
public_html/pl-PL/toc.html | 9 +
public_html/pt-BR/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pt-BR/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pt-BR/opds-Fedora_Core.xml | 2 +-
public_html/pt-BR/opds-Fedora_Documentation.xml | 2 +-
.../pt-BR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pt-BR/opds-Fedora_Security_Team.xml | 2 +-
public_html/pt-BR/opds.xml | 16 +-
public_html/pt-BR/toc.html | 9 +
public_html/pt-PT/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pt-PT/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pt-PT/opds-Fedora_Core.xml | 2 +-
public_html/pt-PT/opds-Fedora_Documentation.xml | 2 +-
.../pt-PT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pt-PT/opds-Fedora_Security_Team.xml | 2 +-
public_html/pt-PT/opds.xml | 16 +-
public_html/pt-PT/toc.html | 9 +
public_html/ro/Site_Statistics.html | 4 +-
.../ro/opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ro/opds-Fedora.xml | 20 +-
.../ro/opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ro/opds-Fedora_Core.xml | 2 +-
public_html/ro/opds-Fedora_Documentation.xml | 2 +-
public_html/ro/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ro/opds-Fedora_Security_Team.xml | 2 +-
public_html/ro/opds.xml | 16 +-
public_html/ro/toc.html | 9 +
public_html/ru-RU/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ru-RU/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ru-RU/opds-Fedora_Core.xml | 2 +-
public_html/ru-RU/opds-Fedora_Documentation.xml | 2 +-
.../ru-RU/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ru-RU/opds-Fedora_Security_Team.xml | 2 +-
public_html/ru-RU/opds.xml | 16 +-
public_html/ru-RU/toc.html | 9 +
public_html/sk-SK/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sk-SK/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sk-SK/opds-Fedora_Core.xml | 2 +-
public_html/sk-SK/opds-Fedora_Documentation.xml | 2 +-
.../sk-SK/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sk-SK/opds-Fedora_Security_Team.xml | 2 +-
public_html/sk-SK/opds.xml | 16 +-
public_html/sk-SK/toc.html | 9 +
public_html/sr-Latn-RS/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sr-Latn-RS/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sr-Latn-RS/opds-Fedora_Core.xml | 2 +-
.../sr-Latn-RS/opds-Fedora_Documentation.xml | 2 +-
.../sr-Latn-RS/opds-Fedora_Draft_Documentation.xml | 2 +-
.../sr-Latn-RS/opds-Fedora_Security_Team.xml | 2 +-
public_html/sr-Latn-RS/opds.xml | 16 +-
public_html/sr-Latn-RS/toc.html | 9 +
public_html/sr-RS/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sr-RS/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sr-RS/opds-Fedora_Core.xml | 2 +-
public_html/sr-RS/opds-Fedora_Documentation.xml | 2 +-
.../sr-RS/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sr-RS/opds-Fedora_Security_Team.xml | 2 +-
public_html/sr-RS/opds.xml | 16 +-
public_html/sr-RS/toc.html | 9 +
public_html/sv-SE/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sv-SE/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sv-SE/opds-Fedora_Core.xml | 2 +-
public_html/sv-SE/opds-Fedora_Documentation.xml | 2 +-
.../sv-SE/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sv-SE/opds-Fedora_Security_Team.xml | 2 +-
public_html/sv-SE/opds.xml | 16 +-
public_html/sv-SE/toc.html | 9 +
public_html/ta-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ta-IN/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ta-IN/opds-Fedora_Core.xml | 2 +-
public_html/ta-IN/opds-Fedora_Documentation.xml | 2 +-
.../ta-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ta-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/ta-IN/opds.xml | 16 +-
public_html/ta-IN/toc.html | 9 +
public_html/te-IN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/te-IN/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/te-IN/opds-Fedora_Core.xml | 2 +-
public_html/te-IN/opds-Fedora_Documentation.xml | 2 +-
.../te-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/te-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/te-IN/opds.xml | 16 +-
public_html/te-IN/toc.html | 9 +
public_html/toc.html | 15 +
public_html/uk-UA/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/uk-UA/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/uk-UA/opds-Fedora_Core.xml | 2 +-
public_html/uk-UA/opds-Fedora_Documentation.xml | 2 +-
.../uk-UA/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/uk-UA/opds-Fedora_Security_Team.xml | 2 +-
public_html/uk-UA/opds.xml | 16 +-
public_html/uk-UA/toc.html | 9 +
public_html/zh-CN/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/zh-CN/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/zh-CN/opds-Fedora_Core.xml | 2 +-
public_html/zh-CN/opds-Fedora_Documentation.xml | 2 +-
.../zh-CN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/zh-CN/opds-Fedora_Security_Team.xml | 2 +-
public_html/zh-CN/opds.xml | 16 +-
public_html/zh-CN/toc.html | 9 +
public_html/zh-TW/Site_Statistics.html | 4 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/zh-TW/opds-Fedora.xml | 20 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/zh-TW/opds-Fedora_Core.xml | 2 +-
public_html/zh-TW/opds-Fedora_Documentation.xml | 2 +-
.../zh-TW/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/zh-TW/opds-Fedora_Security_Team.xml | 2 +-
public_html/zh-TW/opds.xml | 16 +-
public_html/zh-TW/toc.html | 9 +
827 files changed, 19154 insertions(+), 812 deletions(-)
---
diff --git a/fedoradocs.db b/fedoradocs.db
index b1012da..51f3dd4 100755
Binary files a/fedoradocs.db and b/fedoradocs.db differ
diff --git a/public_html/Sitemap b/public_html/Sitemap
index 5df101e..cefbdb9 100644
--- a/public_html/Sitemap
+++ b/public_html/Sitemap
@@ -1975,6 +1975,30 @@
<priority>0.8</priority>
</url>
<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</loc>
+ <lastmod>2015-01-08</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora/21/html/Networking_Guide/index.html</loc>
+ <lastmod>2015-01-08</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora/21/html-single/Networking_Guide/index.html</loc>
+ <lastmod>2015-01-08</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf</loc>
+ <lastmod>2015-01-08</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</loc>
<lastmod>2014-12-09</lastmod>
<changefreq>monthly</changefreq>
diff --git a/public_html/as-IN/Site_Statistics.html b/public_html/as-IN/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/as-IN/Site_Statistics.html
+++ b/public_html/as-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/as-IN/opds-Community_Services_Infrastructure.xml b/public_html/as-IN/opds-Community_Services_Infrastructure.xml
index 9b28273..89c06c1 100644
--- a/public_html/as-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/as-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:14</updated>
+ <updated>2015-01-08T14:06:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora.xml b/public_html/as-IN/opds-Fedora.xml
index 131ec1c..ef3002a 100644
--- a/public_html/as-IN/opds-Fedora.xml
+++ b/public_html/as-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:14</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>as-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
index 96891af..c7fc45e 100644
--- a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Core.xml b/public_html/as-IN/opds-Fedora_Core.xml
index 3fcaa27..c34436f 100644
--- a/public_html/as-IN/opds-Fedora_Core.xml
+++ b/public_html/as-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Documentation.xml b/public_html/as-IN/opds-Fedora_Documentation.xml
index 293e88a..cf3a1b6 100644
--- a/public_html/as-IN/opds-Fedora_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Draft_Documentation.xml b/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
index e290d69..a73765d 100644
--- a/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Security_Team.xml b/public_html/as-IN/opds-Fedora_Security_Team.xml
index 394fcc2..001efa7 100644
--- a/public_html/as-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/as-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds.xml b/public_html/as-IN/opds.xml
index c53d765..9c7a7d4 100644
--- a/public_html/as-IN/opds.xml
+++ b/public_html/as-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/as-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/as-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:14</updated>
+ <updated>2015-01-08T14:06:20</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:14</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/as-IN/toc.html b/public_html/as-IN/toc.html
index 872e918..63e58dc 100644
--- a/public_html/as-IN/toc.html
+++ b/public_html/as-IN/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/bg-BG/Site_Statistics.html b/public_html/bg-BG/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/bg-BG/Site_Statistics.html
+++ b/public_html/bg-BG/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/bg-BG/opds-Community_Services_Infrastructure.xml b/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
index 6fbd398..c3b464c 100644
--- a/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
+++ b/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora.xml b/public_html/bg-BG/opds-Fedora.xml
index 4d0be9a..75afe03 100644
--- a/public_html/bg-BG/opds-Fedora.xml
+++ b/public_html/bg-BG/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>bg-BG</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
index da13aa2..487b030 100644
--- a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Core.xml b/public_html/bg-BG/opds-Fedora_Core.xml
index 9e8ddbc..d490cb7 100644
--- a/public_html/bg-BG/opds-Fedora_Core.xml
+++ b/public_html/bg-BG/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Documentation.xml b/public_html/bg-BG/opds-Fedora_Documentation.xml
index dec058e..5eb0b71 100644
--- a/public_html/bg-BG/opds-Fedora_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml b/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
index b8057b0..98e50c1 100644
--- a/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Security_Team.xml b/public_html/bg-BG/opds-Fedora_Security_Team.xml
index 7a07e32..e07741c 100644
--- a/public_html/bg-BG/opds-Fedora_Security_Team.xml
+++ b/public_html/bg-BG/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds.xml b/public_html/bg-BG/opds.xml
index 00c3901..c1b3141 100644
--- a/public_html/bg-BG/opds.xml
+++ b/public_html/bg-BG/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bg-BG/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/bg-BG/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/bg-BG/toc.html b/public_html/bg-BG/toc.html
index 7cf3dce..d0a6218 100644
--- a/public_html/bg-BG/toc.html
+++ b/public_html/bg-BG/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/bn-IN/Site_Statistics.html b/public_html/bn-IN/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/bn-IN/Site_Statistics.html
+++ b/public_html/bn-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/bn-IN/opds-Community_Services_Infrastructure.xml b/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
index 50ccafd..cb91bee 100644
--- a/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora.xml b/public_html/bn-IN/opds-Fedora.xml
index 6fe74b9..fb76089 100644
--- a/public_html/bn-IN/opds-Fedora.xml
+++ b/public_html/bn-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>bn-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
index 6a3c3da..bd96e9c 100644
--- a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Core.xml b/public_html/bn-IN/opds-Fedora_Core.xml
index bf18e92..94c4eb4 100644
--- a/public_html/bn-IN/opds-Fedora_Core.xml
+++ b/public_html/bn-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Documentation.xml b/public_html/bn-IN/opds-Fedora_Documentation.xml
index 4488b9e..928bf44 100644
--- a/public_html/bn-IN/opds-Fedora_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml b/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
index e3bf60d..ec891a3 100644
--- a/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Security_Team.xml b/public_html/bn-IN/opds-Fedora_Security_Team.xml
index 645307d..fe354bb 100644
--- a/public_html/bn-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/bn-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds.xml b/public_html/bn-IN/opds.xml
index 36e8fbf..0e2d026 100644
--- a/public_html/bn-IN/opds.xml
+++ b/public_html/bn-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bn-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/bn-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/bn-IN/toc.html b/public_html/bn-IN/toc.html
index 55fedfb..5f67ab2 100644
--- a/public_html/bn-IN/toc.html
+++ b/public_html/bn-IN/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/bs-BA/Site_Statistics.html b/public_html/bs-BA/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/bs-BA/Site_Statistics.html
+++ b/public_html/bs-BA/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/bs-BA/opds-Community_Services_Infrastructure.xml b/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
index 128baec..11a42c0 100644
--- a/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
+++ b/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora.xml b/public_html/bs-BA/opds-Fedora.xml
index 0f21537..0f60d39 100644
--- a/public_html/bs-BA/opds-Fedora.xml
+++ b/public_html/bs-BA/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>bs-BA</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
index dbb7d59..63226f4 100644
--- a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Core.xml b/public_html/bs-BA/opds-Fedora_Core.xml
index 39b2dd4..5275c9e 100644
--- a/public_html/bs-BA/opds-Fedora_Core.xml
+++ b/public_html/bs-BA/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Documentation.xml b/public_html/bs-BA/opds-Fedora_Documentation.xml
index 380a06f..ae52344 100644
--- a/public_html/bs-BA/opds-Fedora_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml b/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
index 251a9a2..0ab768a 100644
--- a/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Security_Team.xml b/public_html/bs-BA/opds-Fedora_Security_Team.xml
index 02621eb..ac19092 100644
--- a/public_html/bs-BA/opds-Fedora_Security_Team.xml
+++ b/public_html/bs-BA/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds.xml b/public_html/bs-BA/opds.xml
index 7e05225..c9c271e 100644
--- a/public_html/bs-BA/opds.xml
+++ b/public_html/bs-BA/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bs-BA/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/bs-BA/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/bs-BA/toc.html b/public_html/bs-BA/toc.html
index c3df7ec..ccaf72e 100644
--- a/public_html/bs-BA/toc.html
+++ b/public_html/bs-BA/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/ca-ES/Site_Statistics.html b/public_html/ca-ES/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/ca-ES/Site_Statistics.html
+++ b/public_html/ca-ES/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/ca-ES/opds-Community_Services_Infrastructure.xml b/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
index cea0b68..66369fa 100644
--- a/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora.xml b/public_html/ca-ES/opds-Fedora.xml
index f2e77fb..4ee1858 100644
--- a/public_html/ca-ES/opds-Fedora.xml
+++ b/public_html/ca-ES/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>ca-ES</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
index 0a0ff09..8805dd2 100644
--- a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Core.xml b/public_html/ca-ES/opds-Fedora_Core.xml
index 03126f7..71e4e9a 100644
--- a/public_html/ca-ES/opds-Fedora_Core.xml
+++ b/public_html/ca-ES/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Documentation.xml b/public_html/ca-ES/opds-Fedora_Documentation.xml
index cf3b963..04feb3e 100644
--- a/public_html/ca-ES/opds-Fedora_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml b/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
index 43d9df9..de9de6a 100644
--- a/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Security_Team.xml b/public_html/ca-ES/opds-Fedora_Security_Team.xml
index 2bd5e5d..62a5c66 100644
--- a/public_html/ca-ES/opds-Fedora_Security_Team.xml
+++ b/public_html/ca-ES/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds.xml b/public_html/ca-ES/opds.xml
index bd6275c..601ac2a 100644
--- a/public_html/ca-ES/opds.xml
+++ b/public_html/ca-ES/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ca-ES/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ca-ES/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ca-ES/toc.html b/public_html/ca-ES/toc.html
index 44f473c..e734520 100644
--- a/public_html/ca-ES/toc.html
+++ b/public_html/ca-ES/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/cs-CZ/Site_Statistics.html b/public_html/cs-CZ/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/cs-CZ/Site_Statistics.html
+++ b/public_html/cs-CZ/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml b/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
index f10165b..a86cb6c 100644
--- a/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
+++ b/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora.xml b/public_html/cs-CZ/opds-Fedora.xml
index 04aba9a..e08fce9 100644
--- a/public_html/cs-CZ/opds-Fedora.xml
+++ b/public_html/cs-CZ/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>cs-CZ</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
index e24583a..bb76291 100644
--- a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Core.xml b/public_html/cs-CZ/opds-Fedora_Core.xml
index bde7a33..a478557 100644
--- a/public_html/cs-CZ/opds-Fedora_Core.xml
+++ b/public_html/cs-CZ/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Documentation.xml
index 785c944..542d11c 100644
--- a/public_html/cs-CZ/opds-Fedora_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
index 5d7d1e1..e6f0c73 100644
--- a/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Security_Team.xml b/public_html/cs-CZ/opds-Fedora_Security_Team.xml
index 8037202..6842893 100644
--- a/public_html/cs-CZ/opds-Fedora_Security_Team.xml
+++ b/public_html/cs-CZ/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds.xml b/public_html/cs-CZ/opds.xml
index ee540dc..3f531d5 100644
--- a/public_html/cs-CZ/opds.xml
+++ b/public_html/cs-CZ/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/cs-CZ/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/cs-CZ/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/cs-CZ/toc.html b/public_html/cs-CZ/toc.html
index 04f8434..50bbcb8 100644
--- a/public_html/cs-CZ/toc.html
+++ b/public_html/cs-CZ/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/da-DK/Site_Statistics.html b/public_html/da-DK/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/da-DK/Site_Statistics.html
+++ b/public_html/da-DK/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/da-DK/opds-Community_Services_Infrastructure.xml b/public_html/da-DK/opds-Community_Services_Infrastructure.xml
index ed6554f..18e09f9 100644
--- a/public_html/da-DK/opds-Community_Services_Infrastructure.xml
+++ b/public_html/da-DK/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora.xml b/public_html/da-DK/opds-Fedora.xml
index 6bf9fcf..306e318 100644
--- a/public_html/da-DK/opds-Fedora.xml
+++ b/public_html/da-DK/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>da-DK</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
index deb4435..74746c7 100644
--- a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Core.xml b/public_html/da-DK/opds-Fedora_Core.xml
index c54c3ee..2e8158c 100644
--- a/public_html/da-DK/opds-Fedora_Core.xml
+++ b/public_html/da-DK/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Documentation.xml b/public_html/da-DK/opds-Fedora_Documentation.xml
index 308aca6..4454cec 100644
--- a/public_html/da-DK/opds-Fedora_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Draft_Documentation.xml b/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
index 1c8af10..6a840c4 100644
--- a/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Security_Team.xml b/public_html/da-DK/opds-Fedora_Security_Team.xml
index 0a2aec8..c587fd2 100644
--- a/public_html/da-DK/opds-Fedora_Security_Team.xml
+++ b/public_html/da-DK/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds.xml b/public_html/da-DK/opds.xml
index 922cdf2..28af034 100644
--- a/public_html/da-DK/opds.xml
+++ b/public_html/da-DK/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/da-DK/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/da-DK/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/da-DK/toc.html b/public_html/da-DK/toc.html
index d9c3d80..46e4287 100644
--- a/public_html/da-DK/toc.html
+++ b/public_html/da-DK/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/de-DE/Site_Statistics.html b/public_html/de-DE/Site_Statistics.html
index b41468b..3761585 100644
--- a/public_html/de-DE/Site_Statistics.html
+++ b/public_html/de-DE/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Sprachen gesamt: </b>45<br />
- <b>Pakete gesamt: </b>917
+ <b>Pakete gesamt: </b>918
</div>
</body>
</html>
diff --git a/public_html/de-DE/opds-Community_Services_Infrastructure.xml b/public_html/de-DE/opds-Community_Services_Infrastructure.xml
index 7ef64ba..1b21f69 100644
--- a/public_html/de-DE/opds-Community_Services_Infrastructure.xml
+++ b/public_html/de-DE/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora.xml b/public_html/de-DE/opds-Fedora.xml
index 6ff49f7..2b3b9f1 100644
--- a/public_html/de-DE/opds-Fedora.xml
+++ b/public_html/de-DE/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>de-DE</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
index fb8a53b..0d03ab2 100644
--- a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Core.xml b/public_html/de-DE/opds-Fedora_Core.xml
index 9bcf8b8..00a6595 100644
--- a/public_html/de-DE/opds-Fedora_Core.xml
+++ b/public_html/de-DE/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Documentation.xml b/public_html/de-DE/opds-Fedora_Documentation.xml
index 5404a67..0a029c3 100644
--- a/public_html/de-DE/opds-Fedora_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Draft_Documentation.xml b/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
index b58579b..7443417 100644
--- a/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Security_Team.xml b/public_html/de-DE/opds-Fedora_Security_Team.xml
index 1fbd972..bd99011 100644
--- a/public_html/de-DE/opds-Fedora_Security_Team.xml
+++ b/public_html/de-DE/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds.xml b/public_html/de-DE/opds.xml
index fdff194..7eb844e 100644
--- a/public_html/de-DE/opds.xml
+++ b/public_html/de-DE/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/de-DE/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/de-DE/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/de-DE/toc.html b/public_html/de-DE/toc.html
index d88cd5f..1f5886b 100644
--- a/public_html/de-DE/toc.html
+++ b/public_html/de-DE/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/el-GR/Site_Statistics.html b/public_html/el-GR/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/el-GR/Site_Statistics.html
+++ b/public_html/el-GR/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/el-GR/opds-Community_Services_Infrastructure.xml b/public_html/el-GR/opds-Community_Services_Infrastructure.xml
index e217b07..e6e4cd2 100644
--- a/public_html/el-GR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/el-GR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora.xml b/public_html/el-GR/opds-Fedora.xml
index 3c3a8d7..d547b93 100644
--- a/public_html/el-GR/opds-Fedora.xml
+++ b/public_html/el-GR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>el-GR</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
index f50f571..110318c 100644
--- a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Core.xml b/public_html/el-GR/opds-Fedora_Core.xml
index 261e22f..d37db21 100644
--- a/public_html/el-GR/opds-Fedora_Core.xml
+++ b/public_html/el-GR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Documentation.xml b/public_html/el-GR/opds-Fedora_Documentation.xml
index 7e3836d..df1ba7d 100644
--- a/public_html/el-GR/opds-Fedora_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Draft_Documentation.xml b/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
index fbda09a..39c5cb6 100644
--- a/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Security_Team.xml b/public_html/el-GR/opds-Fedora_Security_Team.xml
index cb91642..ce86a8f 100644
--- a/public_html/el-GR/opds-Fedora_Security_Team.xml
+++ b/public_html/el-GR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds.xml b/public_html/el-GR/opds.xml
index c282071..4e839bf 100644
--- a/public_html/el-GR/opds.xml
+++ b/public_html/el-GR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/el-GR/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/el-GR/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/el-GR/toc.html b/public_html/el-GR/toc.html
index b960aee..95f5f4a 100644
--- a/public_html/el-GR/toc.html
+++ b/public_html/el-GR/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub b/public_html/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub
new file mode 100644
index 0000000..fd5900f
Binary files /dev/null and b/public_html/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/css/common.css b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..d7dc3f2
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/css/common.css
@@ -0,0 +1,1528 @@
+* {
+ widows: 2 !important;
+ orphans: 2 !important;
+}
+
+body, h1, h2, h3, h4, h5, h6, pre, li, div {
+ line-height: 1.29em;
+}
+
+body {
+ background-color: white;
+ margin:0 auto;
+ font-family: "liberation sans", "Myriad ", "Bitstream Vera Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS", helvetica, verdana, arial, sans-serif;
+ font-size:12px;
+ max-width:55em;
+ color:black;
+}
+
+body.toc_embeded {
+ /*for web hosting system only*/
+ margin-left: 300px;
+}
+
+object.toc, iframe.toc {
+ /*for web hosting system only*/
+ border-style:none;
+ position:fixed;
+ width:290px;
+ height:99.99%;
+ top:0;
+ left:0;
+ z-index: 100;
+ border-style:none;
+ border-right:1px solid #999;
+}
+
+/* Hide web menu */
+
+body.notoc {
+ margin-left: 3em;
+}
+
+iframe.notoc {
+ border-style:none;
+ border: none;
+ padding: 0em;
+ position:fixed;
+ width: 21px;
+ height: 29px;
+ top: 0px;
+ left:0;
+ overflow: hidden;
+ margin: 0em;
+ margin-left: -3px;
+}
+/* End hide web menu */
+
+/* desktop styles */
+body.desktop {
+ margin-left: 26em;
+}
+
+body.desktop .book > .toc {
+ display:block;
+ width:24em;
+ height:99%;
+ position:fixed;
+ overflow:auto;
+ top:0px;
+ left:0px;
+ padding-left:1em;
+ background-color:#EEEEEE;
+}
+
+.toc {
+ line-height:1.35em;
+}
+
+.toc .glossary,
+.toc .chapter, .toc .appendix {
+ margin-top:1em;
+}
+
+.toc .part {
+ margin-top:1em;
+ display:block;
+}
+
+span.glossary,
+span.appendix {
+ display:block;
+ margin-top:0.5em;
+}
+
+div {
+ padding-top:0px;
+}
+
+div.section {
+ padding-top:1em;
+}
+
+p, div.para, div.formalpara {
+ padding-top:0px;
+ margin-top:0.3em;
+ padding-bottom:0px;
+ margin-bottom:1em;
+}
+
+/*Links*/
+a {
+ outline: none;
+}
+
+a:link {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#3366cc;
+}
+
+a:visited {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#003366;
+}
+
+div.longdesc-link {
+ float:right;
+ color:#999;
+}
+
+.toc a, .qandaset a {
+ font-weight:normal;
+ border:none;
+}
+
+.toc a:hover, .qandaset a:hover
+{
+ border-bottom: 1px dotted;
+}
+
+/*headings*/
+h1, h2, h3, h4, h5, h6 {
+ color: #336699;
+ margin-top: 0em;
+ margin-bottom: 0em;
+ background-color: transparent;
+ page-break-inside: avoid;
+ page-break-after: avoid;
+}
+
+h1 {
+ font-size:2.0em;
+}
+
+.titlepage h1.title {
+ font-size: 3.0em;
+ padding-top: 1em;
+ text-align:left;
+}
+
+.book > .titlepage h1.title {
+ text-align:center;
+}
+
+.article > .titlepage h1.title {
+ text-align:center;
+}
+
+.set .titlepage > div > div > h1.title {
+ text-align:center;
+}
+
+.producttitle {
+ margin-top: 0em;
+ margin-bottom: 0em;
+ font-size: 3.0em;
+ font-weight: bold;
+ background: #003d6e url(../images/h1-bg.png) top left repeat-x;
+ color: white;
+ text-align: center;
+ padding: 0.7em;
+}
+
+.titlepage .corpauthor {
+ margin-top: 1em;
+ text-align: center;
+}
+
+.section h1.title {
+ font-size: 1.6em;
+ padding: 0em;
+ color: #336699;
+ text-align: left;
+ background: white;
+}
+
+h2 {
+ font-size:1.6em;
+}
+
+
+h2.subtitle, h3.subtitle {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ text-align: center;
+}
+
+.preface > div > div > div > h2.title {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+.appendix h2 {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+
+
+h3 {
+ font-size:1.3em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+h4 {
+ font-size:1.1em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h5 {
+ font-size:1em;
+}
+
+h6 {
+ font-size:1em;
+}
+
+h5.formalpara {
+ font-size:1em;
+ margin-top:2em;
+ margin-bottom:.8em;
+}
+
+.abstract h6 {
+ margin-top:1em;
+ margin-bottom:.5em;
+ font-size:2em;
+}
+
+/*element rules*/
+hr {
+ border-collapse: collapse;
+ border-style:none;
+ border-top: 1px dotted #ccc;
+ width:100%;
+ margin-top: 3em;
+}
+
+/* web site rules */
+ul.languages, .languages li {
+ display:inline;
+ padding:0em;
+}
+
+.languages li a {
+ padding:0em .5em;
+ text-decoration: none;
+}
+
+.languages li p, .languages li div.para {
+ display:inline;
+}
+
+.languages li a:link, .languages li a:visited {
+ color:#444;
+}
+
+.languages li a:hover, .languages li a:focus, .languages li a:active {
+ color:black;
+}
+
+ul.languages {
+ display:block;
+ background-color:#eee;
+ padding:.5em;
+}
+
+/*supporting stylesheets*/
+
+/*unique to the webpage only*/
+.books {
+ position:relative;
+}
+
+.versions li {
+ width:100%;
+ clear:both;
+ display:block;
+}
+
+a.version {
+ font-size:2em;
+ text-decoration:none;
+ width:100%;
+ display:block;
+ padding:1em 0em .2em 0em;
+ clear:both;
+}
+
+a.version:before {
+ content:"Version";
+ font-size:smaller;
+}
+
+a.version:visited, a.version:link {
+ color:#666;
+}
+
+a.version:focus, a.version:hover {
+ color:black;
+}
+
+.books {
+ display:block;
+ position:relative;
+ clear:both;
+ width:100%;
+}
+
+.books li {
+ display:block;
+ width:200px;
+ float:left;
+ position:relative;
+ clear: none ;
+}
+
+.books .html {
+ width:170px;
+ display:block;
+}
+
+.books .pdf {
+ position:absolute;
+ left:170px;
+ top:0px;
+ font-size:smaller;
+}
+
+.books .pdf:link, .books .pdf:visited {
+ color:#555;
+}
+
+.books .pdf:hover, .books .pdf:focus {
+ color:#000;
+}
+
+.books li a {
+ text-decoration:none;
+}
+
+.books li a:hover {
+ color:black;
+}
+
+/*products*/
+.products li {
+ display: block;
+ width:300px;
+ float:left;
+}
+
+.products li a {
+ width:300px;
+ padding:.5em 0em;
+}
+
+.products ul {
+ clear:both;
+}
+
+/*revision history*/
+.revhistory {
+ display:block;
+}
+
+.revhistory table {
+ background-color:transparent;
+ border-color:#fff;
+ padding:0em;
+ margin: 0;
+ border-collapse:collapse;
+ border-style:none;
+}
+
+.revhistory td {
+ text-align :left;
+ padding:0em;
+ border: none;
+ border-top: 1px solid #fff;
+ font-weight: bold;
+}
+
+.revhistory .simplelist td {
+ font-weight: normal;
+}
+
+.revhistory .simplelist {
+ margin-bottom: 1.5em;
+ margin-left: 1em;
+}
+
+.revhistory table th {
+ display: none;
+}
+
+
+/*credits*/
+.authorgroup div {
+ clear:both;
+ text-align: center;
+}
+
+h3.author {
+ margin: 0em;
+ padding: 0em;
+ padding-top: 1em;
+}
+
+.authorgroup h4 {
+ padding: 0em;
+ margin: 0em;
+ padding-top: 1em;
+ margin-top: 1em;
+}
+
+.author,
+.editor,
+.translator,
+.othercredit,
+.contrib {
+ display: block;
+}
+
+.revhistory .author {
+ display: inline;
+}
+
+.othercredit h3 {
+ padding-top: 1em;
+}
+
+
+.othercredit {
+ margin:0em;
+ padding:0em;
+}
+
+.releaseinfo {
+ clear: both;
+}
+
+.copyright {
+ margin-top: 1em;
+}
+
+/* qanda sets */
+.answer {
+ margin-bottom:1em;
+ border-bottom:1px dotted #ccc;
+}
+
+.qandaset .toc {
+ border-bottom:1px dotted #ccc;
+}
+
+.question {
+ font-weight:bold;
+}
+
+.answer .data, .question .data {
+ padding-left: 2.6em;
+}
+
+.answer label, .question label {
+ float:left;
+ font-weight:bold;
+}
+
+/* inline syntax highlighting */
+.perl_Alert {
+ color: #0000ff;
+}
+
+.perl_BaseN {
+ color: #007f00;
+}
+
+.perl_BString {
+ color: #5C3566;
+}
+
+.perl_Char {
+ color: #ff00ff;
+}
+
+.perl_Comment {
+ color: #FF00FF;
+}
+
+
+.perl_DataType {
+ color: #0000ff;
+}
+
+
+.perl_DecVal {
+ color: #00007f;
+}
+
+
+.perl_Error {
+ color: #ff0000;
+}
+
+
+.perl_Float {
+ color: #00007f;
+}
+
+
+.perl_Function {
+ color: #007f00;
+}
+
+
+.perl_IString {
+ color: #5C3566;
+}
+
+
+.perl_Keyword {
+ color: #002F5D;
+}
+
+
+.perl_Operator {
+ color: #ffa500;
+}
+
+
+.perl_Others {
+ color: #b03060;
+}
+
+
+.perl_RegionMarker {
+ color: #96b9ff;
+}
+
+
+.perl_Reserved {
+ color: #9b30ff;
+}
+
+
+.perl_String {
+ color: #5C3566;
+}
+
+
+.perl_Variable {
+ color: #0000ff;
+}
+
+
+.perl_Warning {
+ color: #0000ff;
+}
+
+/*Lists*/
+ul {
+ padding-left:1.6em;
+ list-style-image:url(../images/dot.png);
+ list-style-type: circle;
+}
+
+ul ul {
+ list-style-image:url(../images/dot2.png);
+ list-style-type: circle;
+}
+
+ol {
+ list-style-image:none;
+ list-style-type: decimal;
+}
+
+ol ol {
+ list-style-type: lower-alpha;
+}
+
+ol.arabic {
+ list-style-type: decimal;
+}
+
+ol.loweralpha {
+ list-style-type: lower-alpha;
+}
+
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+dt {
+ font-weight:bold;
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+dd {
+ margin:0em;
+ margin-left:2em;
+ padding-top:0em;
+ padding-bottom: 1em;
+}
+
+li {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.4em;
+}
+
+li p, li div.para {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.3em;
+}
+
+/*images*/
+img {
+ display:block;
+ margin: 2em 0;
+}
+
+.inlinemediaobject, .inlinemediaobject img {
+ display:inline;
+ margin:0em;
+}
+
+.figure img {
+ display:block;
+ margin:0;
+ page-break-inside: avoid;
+}
+
+.figure .title {
+ margin:0em;
+ margin-bottom:2em;
+ padding:0px;
+}
+
+/*document modes*/
+.confidential {
+ background-color:#900;
+ color:White;
+ padding:.5em .5em;
+ text-transform:uppercase;
+ text-align:center;
+}
+
+.longdesc-link {
+ display:none;
+}
+
+.longdesc {
+ display:none;
+}
+
+.prompt {
+ padding:0em .3em;
+}
+
+/*user interface styles*/
+.screen .replaceable {
+}
+
+.guibutton, .guilabel {
+ font-family: "liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight: bold;
+ white-space: nowrap;
+}
+
+.example {
+ background-color: #ffffff;
+ border-left: 3px solid #aaaaaa;
+ padding-top: 1em;
+ padding-bottom: 0.1em;
+}
+
+.example h6 {
+ padding-left: 10px;
+}
+
+.example-contents {
+ padding-left: 10px;
+ background-color: #ffffff;
+}
+
+.example-contents .para {
+/* padding: 10px;*/
+}
+
+/*terminal/console text*/
+.computeroutput,
+.option {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+.replaceable {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-style: italic;
+}
+
+.command, .filename, .keycap, .classname, .literal {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+/* no bold in toc */
+.toc * {
+ font-weight: inherit;
+}
+
+pre {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ display:block;
+ background-color: #f5f5f5;
+ color: #000000;
+ border: 1px solid #aaaaaa;
+ margin-bottom: 0.3em;
+ padding:.5em 1em;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+ font-size: 0.9em;
+}
+
+pre .replaceable,
+pre .keycap {
+}
+
+code {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+/* white-space: nowrap;*/
+ white-space: pre-wrap;
+ word-wrap: break-word;
+ font-weight:bold;
+}
+
+.parameter code {
+ display: inline;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+}
+
+/*Notifications*/
+div.warning:before {
+ content:url(../images/warning.png);
+ padding-left: 5px;
+}
+
+div.note:before {
+ content:url(../images/note.png);
+ padding-left: 5px;
+}
+
+div.important:before {
+ content:url(../images/important.png);
+ padding-left: 5px;
+}
+
+div.warning, div.note, div.important {
+ color: black;
+ margin: 0em;
+ padding: 0em;
+ background: none;
+ background-color: white;
+ margin-bottom: 1em;
+ border-bottom: 1px solid #aaaaaa;
+ page-break-inside: avoid;
+}
+
+div.warning h2, div.note h2,div.important h2 {
+ margin: 0em;
+ padding: 0em;
+ color: #eeeeec;
+ padding-top: 0px;
+ padding-bottom: 0px;
+ height: 1.4em;
+ line-height: 1.4em;
+ font-size: 1.4em;
+ display:inline;
+}
+
+div.admonition_header {
+ clear: both;
+ margin: 0em;
+ padding: 0em;
+ margin-top: -3.3em;
+ padding-left: 58px;
+ line-height: 1.0em;
+ font-size: 1.0em;
+}
+
+div.warning div.admonition_header {
+ background: url(../images/red.png) top left repeat-x;
+ background-color: #590000;
+}
+
+div.note div.admonition_header {
+ background: url(../images/green.png) top right repeat-x;
+ background-color: #597800;
+}
+
+div.important div.admonition_header {
+ background: url(../images/yellow.png) top right repeat-x;
+ background-color: #a6710f;
+}
+
+div.warning p, div.warning div.para,
+div.note p, div.note div.para,
+div.important p, div.important div.para {
+ padding: 0em;
+ margin: 0em;
+}
+
+div.admonition {
+ border: none;
+ border-left: 1px solid #aaaaaa;
+ border-right: 1px solid #aaaaaa;
+ padding:0em;
+ margin:0em;
+ padding-top: 1.5em;
+ padding-bottom: 1em;
+ padding-left: 2em;
+ padding-right: 1em;
+ background-color: #eeeeec;
+ -moz-border-radius: 0px;
+ -webkit-border-radius: 0px;
+ border-radius: 0px;
+}
+
+/*Page Title*/
+#title {
+ display:block;
+ height:45px;
+ padding-bottom:1em;
+ margin:0em;
+}
+
+#title a.left{
+ display:inline;
+ border:none;
+}
+
+#title a.left img{
+ border:none;
+ float:left;
+ margin:0em;
+ margin-top:.7em;
+}
+
+#title a.right {
+ padding-bottom:1em;
+}
+
+#title a.right img {
+ border:none;
+ float:right;
+ margin:0em;
+ margin-top:.7em;
+}
+
+/*Table*/
+div.table {
+ page-break-inside: avoid;
+}
+
+table {
+ border:1px solid #6c614b;
+ width:100%;
+ border-collapse:collapse;
+}
+
+table.simplelist, .calloutlist table {
+ border-style: none;
+}
+
+table th {
+ text-align:left;
+ background-color:#6699cc;
+ padding:.3em .5em;
+ color:white;
+}
+
+table td {
+ padding:.15em .5em;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+table th p:first-child, table td p:first-child, table li p:first-child,
+table th div.para:first-child, table td div.para:first-child, table li div.para:first-child {
+ margin-top:0em;
+ padding-top:0em;
+ display:inline;
+}
+
+th, td {
+ border-style:none;
+ vertical-align: top;
+ border: 1px solid #000;
+}
+
+.simplelist th, .simplelist td {
+ border: none;
+}
+
+table table td {
+ border-bottom:1px dotted #aaa;
+ background-color:white;
+ padding:.6em 0em;
+}
+
+table table {
+ border:1px solid white;
+}
+
+td.remarkval {
+ color:#444;
+}
+
+td.fieldval {
+ font-weight:bold;
+}
+
+.lbname, .lbtype, .lbdescr, .lbdriver, .lbhost {
+ color:white;
+ font-weight:bold;
+ background-color:#999;
+ width:120px;
+}
+
+td.remarkval {
+ width:230px;
+}
+
+td.tname {
+ font-weight:bold;
+}
+
+th.dbfield {
+ width:120px;
+}
+
+th.dbtype {
+ width:70px;
+}
+
+th.dbdefault {
+ width:70px;
+}
+
+th.dbnul {
+ width:70px;
+}
+
+th.dbkey {
+ width:70px;
+}
+
+span.book {
+ margin-top:4em;
+ display:block;
+ font-size:11pt;
+}
+
+span.book a{
+ font-weight:bold;
+}
+span.chapter {
+ display:block;
+ margin-top:0.5em;
+}
+
+table.simplelist td, .calloutlist table td {
+ border-style: none;
+}
+
+/*Breadcrumbs*/
+#breadcrumbs ul li.first:before {
+ content:" ";
+}
+
+#breadcrumbs {
+ color:#900;
+ padding:3px;
+ margin-bottom:25px;
+}
+
+#breadcrumbs ul {
+ margin-left:0;
+ padding-left:0;
+ display:inline;
+ border:none;
+}
+
+#breadcrumbs ul li {
+ margin-left:0;
+ padding-left:2px;
+ border:none;
+ list-style:none;
+ display:inline;
+}
+
+#breadcrumbs ul li:before {
+ content:"\0020 \0020 \0020 \00BB \0020";
+ color:#333;
+}
+
+/*index*/
+.glossary h3,
+.index h3 {
+ font-size: 2em;
+ color:#aaa;
+ margin:0em;
+}
+
+.indexdiv {
+ margin-bottom:1em;
+}
+
+.glossary dt,
+.index dt {
+ color:#444;
+ padding-top:.5em;
+}
+
+.glossary dl dl dt,
+.index dl dl dt {
+ color:#777;
+ font-weight:normal;
+ padding-top:0em;
+}
+
+.index dl dl dt:before {
+ content:"- ";
+ color:#ccc;
+}
+
+/*changes*/
+.footnote {
+ font-size: .7em;
+ margin:0em;
+ color:#222;
+}
+
+table .footnote {
+}
+
+sup {
+ color:#999;
+ margin:0em;
+ padding:0em;
+ line-height: .4em;
+ font-size: 1em;
+ padding-left:0em;
+}
+
+.footnote {
+ position:relative;
+}
+
+.footnote sup {
+ color:#e3dcc0;
+ position:absolute;
+ left: .4em;
+}
+
+.footnote sup a:link,
+.footnote sup a:visited {
+ color:#92917d;
+ text-decoration:none;
+}
+
+.footnote:hover sup a {
+ text-decoration:none;
+}
+
+.footnote p,.footnote div.para {
+ padding-left:2em;
+}
+
+.footnote a:link,
+.footnote a:visited {
+ color:#00537c;
+}
+
+.footnote a:hover {
+}
+
+/**/
+div.chapter {
+ margin-top:3em;
+ page-break-inside: avoid;
+}
+
+div.preface {
+ page-break-inside: avoid;
+}
+
+div.section {
+ margin-top:1em;
+ page-break-inside: auto;
+}
+
+div.note .replaceable,
+div.important .replaceable,
+div.warning .replaceable,
+div.note .keycap,
+div.important .keycap,
+div.warning .keycap
+{
+}
+
+ul li p:last-child, ul li div.para:last-child {
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+/*document navigation*/
+.docnav a, .docnav strong {
+ border:none;
+ text-decoration:none;
+ font-weight:normal;
+}
+
+.docnav {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ position:relative;
+ width:100%;
+ padding-bottom:2em;
+ padding-top:1em;
+ border-top:1px dotted #ccc;
+}
+
+.docnav li {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ display:inline;
+ font-size:.8em;
+}
+
+.docnav li:before {
+ content:" ";
+}
+
+.docnav li.previous, .docnav li.next {
+ position:absolute;
+ top:1em;
+}
+
+.docnav li.up, .docnav li.home {
+ margin:0em 1.5em;
+}
+
+.docnav li.previous {
+ left:0px;
+ text-align:left;
+}
+
+.docnav li.next {
+ right:0px;
+ text-align:right;
+}
+
+.docnav li.previous strong, .docnav li.next strong {
+ height:22px;
+ display:block;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+.docnav li.next a strong {
+ background: url(../images/stock-go-forward.png) top right no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-right:28px;
+ font-size:1.2em;
+}
+
+.docnav li.previous a strong {
+ background: url(../images/stock-go-back.png) top left no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-left:28px;
+ padding-right:0.5em;
+ font-size:1.2em;
+}
+
+.docnav li.home a strong {
+ background: url(../images/stock-home.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav li.up a strong {
+ background: url(../images/stock-go-up.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav a:link, .docnav a:visited {
+ color:#666;
+}
+
+.docnav a:hover, .docnav a:focus, .docnav a:active {
+ color:black;
+}
+
+.docnav a {
+ max-width: 10em;
+ overflow:hidden;
+}
+
+.docnav a:link strong {
+ text-decoration:none;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+ul.docnav {
+ margin-bottom: 1em;
+}
+/* Reports */
+.reports ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.reports li{
+ margin:0em;
+ padding:0em;
+}
+
+.reports li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.reports dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.reports h2, .reports h3{
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.reports div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/*uniform*/
+body.results, body.reports {
+ max-width:57em ;
+ padding:0em;
+}
+
+/*Progress Bar*/
+div.progress {
+ display:block;
+ float:left;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ height:1em;
+}
+
+div.progress span {
+ height:1em;
+ float:left;
+}
+
+div.progress span.translated {
+ background:#6c3 url(../images/shine.png) top left repeat-x;
+}
+
+div.progress span.fuzzy {
+ background:#ff9f00 url(../images/shine.png) top left repeat-x;
+}
+
+
+/*Results*/
+
+.results ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.results li{
+ margin:0em;
+ padding:0em;
+}
+
+.results li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.results dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.results dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.results dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.results h2, .results h3 {
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.results div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/* Dirty EVIL Mozilla hack for round corners */
+pre {
+ -moz-border-radius:11px;
+ -webkit-border-radius:11px;
+ border-radius: 11px;
+ page-break-inside: avoid;
+}
+
+.example {
+ -moz-border-radius:0px;
+ -webkit-border-radius:0px;
+ border-radius: 0px;
+ page-break-inside: avoid;
+}
+
+.package, .citetitle {
+ font-style: italic;
+}
+
+.titlepage .edition {
+ color: #336699;
+ background-color: transparent;
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ font-weight: bold;
+ text-align: center;
+}
+
+span.remark {
+ background-color: #ff00ff;
+}
+
+.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+.foreignphrase {
+ font-style: inherit;
+}
+
+dt {
+ clear:both;
+}
+
+dt img {
+ border-style: none;
+ max-width: 112px;
+}
+
+dt object {
+ max-width: 112px;
+}
+
+dt .inlinemediaobject, dt object {
+ display: inline;
+ float: left;
+ margin-bottom: 1em;
+ padding-right: 1em;
+ width: 112px;
+}
+
+dl:after {
+ display: block;
+ clear: both;
+ content: "";
+}
+
+.toc dd {
+ padding-bottom: 0em;
+ margin-bottom: 1em;
+ padding-left: 1.3em;
+ margin-left: 0em;
+}
+
+div.toc > dl > dt {
+ padding-bottom: 0em;
+ margin-bottom: 0em;
+ margin-top: 1em;
+}
+
+
+.strikethrough {
+ text-decoration: line-through;
+}
+
+.underline {
+ text-decoration: underline;
+}
+
+.calloutlist img, .callout {
+ padding: 0em;
+ margin: 0em;
+ width: 12pt;
+ display: inline;
+ vertical-align: middle;
+}
+
+.stepalternatives {
+ list-style-image: none;
+ list-style-type: none;
+}
+
+
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/css/default.css b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/css/lang.css b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/css/overrides.css b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..057be29
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/css/overrides.css
@@ -0,0 +1,51 @@
+a:link {
+ color:#0066cc;
+}
+
+a:hover, a:active {
+ color:#003366;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+
+h1 {
+ color:#3c6eb4
+}
+
+.producttitle {
+ background: #3c6eb4 url(../images/h1-bg.png) top left repeat;
+}
+
+.section h1.title {
+ color:#3c6eb4;
+}
+
+
+h2,h3,h4,h5,h6 {
+ color:#3c6eb4;
+}
+
+table {
+ border:1px solid #3c6eb4;
+}
+
+table th {
+ background-color:#3c6eb4;
+}
+
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.revhistory table th {
+ color:#3c6eb4;
+}
+
+.titlepage .edition {
+ color: #3c6eb4;
+}
+
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/css/print.css b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/1.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..c21d7a3
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/1.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/1.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..a2b3903
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/1.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#000000;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 17.853468,22.008438 -2.564941,0 0,-7.022461 c -5e-6,-0.143873 -5e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224122,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08854,0.08302 -0.17432,0.157723 -0.257324,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/10.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..15b81da
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/10.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/10.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..af015ab
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/10.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/11.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..2fcc2dd
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/11.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/11.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..cb82b70
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/11.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/12.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..edebe20
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/12.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/12.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..3b6d822
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/12.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/13.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..ec48cef
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/13.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/13.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..226e461
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/13.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/14.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..33d5637
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/14.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/14.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..5aaa3a3
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/14.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/15.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..f1a4eb2
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/15.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/15.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..f51dd96
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/15.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2839"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2841"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/16.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..d38a155
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/16.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/16.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..cb7e2f5
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/16.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/17.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..d83e898
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/17.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/17.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..5d6f0ad
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/17.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/18.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..9e39de4
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/18.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/18.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..9ea672c
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/18.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/19.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..9eeedfb
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/19.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/19.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..80d1d09
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/19.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/2.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..ff9cc57
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/2.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/2.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..8e94260
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/2.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.89546,22.008438 -8.143066,0 0,-1.784668 2.855468,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979493,-1.0708 0.293289,-0.326492 0.545079,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.373529,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.17431,-0.666821 0.174316,-1.037598 -6e-6,-0.409496 -0.124517,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827313,0.522958 -1.270019,0.921386 l -1.394531,-1.651855 c 0.249022,-0.226877 0.509113,-0.442698 0.780273,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079102,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319824,-0.1494141 0.58105,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187012,0.6889648 0.326489,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.893727 0.265625,1.41
9433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/20.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..b28b4aa
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/20.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/20.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..409ac6e
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/20.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/21.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..eda952c
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/21.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/21.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..7bc03af
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/21.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/22.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..90b14b0
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/22.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/22.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..fe086f6
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/22.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/23.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..8b35a74
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/23.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/23.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..f17ec29
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/23.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/24.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/24.png
new file mode 100644
index 0000000..6041b02
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/24.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/24.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/24.svg
new file mode 100644
index 0000000..42a5333
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/24.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/25.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/25.png
new file mode 100644
index 0000000..ecb15e6
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/25.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/25.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/25.svg
new file mode 100644
index 0000000..a8d4672
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/25.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/26.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/26.png
new file mode 100644
index 0000000..4b2f560
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/26.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/26.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/26.svg
new file mode 100644
index 0000000..3cf00ec
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/26.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/27.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/27.png
new file mode 100644
index 0000000..ecf058e
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/27.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/27.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/27.svg
new file mode 100644
index 0000000..c8d6440
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/27.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/28.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/28.png
new file mode 100644
index 0000000..e64efb2
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/28.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/28.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/28.svg
new file mode 100644
index 0000000..5acce93
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/28.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/29.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/29.png
new file mode 100644
index 0000000..dbbca1b
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/29.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/29.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/29.svg
new file mode 100644
index 0000000..507dd44
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/29.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/3.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..4febe43
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/3.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/3.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..5e87e1f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/3.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.422316,12.587051 c -9e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.23243,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315437,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.392911,0.332031 -0.890957,0.592122 -1.494141,0.780273 -0.597661,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267255,-0.05534 -1.842773,-0.166016 -0.575523,-0.105143 -1.112306,-0.268392 -1.610352,-0.489746 l 0,-2.183105 c 0.249023,0.132815 0.511881,0.249025 0.788574,0.348632 0.276692,0.09961 0.553384,0.185387 0.830079,0.257325 0.27669,0.06641 0.547848,0.116212 0.813476,0.149414 0.271156,0.0332 0.525713,0.04981 0.763672,0.0498 0.475907,2e-6 0.871577,-0.04427 1.187012,-0.132812 0.315424,-
0.08854 0.567214,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320957,-0.351397 0.398437,-0.572754 0.083,-0.226885 0.124506,-0.473141 0.124512,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.265631,-0.376297 -0.498047,-0.514648 -0.226893,-0.143876 -0.525721,-0.254553 -0.896484,-0.332032 -0.370773,-0.07747 -0.827315,-0.116205 -1.369629,-0.116211 l -0.863281,0 0,-1.801269 0.846679,0 c 0.509111,7e-6 0.932451,-0.04426 1.27002,-0.132813 0.33756,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.43164,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.68897,-0.365224 -1.27002,-0.365234 -0.265629,10e-6 -0.514652,0.02768 -0.74707,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193688,0.07748 -0.373538,0.166026 -0.539551,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439941,0.282227 l -1.294922,-1.70
9961 c 0.232421,-0.171538 0.484211,-0.329253 0.755371,-0.473145 0.276691,-0.143868 0.575519,-0.26838 0.896484,-0.373535 0.320961,-0.1106647 0.666827,-0.1964393 1.037598,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492506,0.1272911 0.913079,0.3154421 1.261718,0.5644531 0.348626,0.243501 0.617017,0.545096 0.805176,0.904786 0.193677,0.354177 0.290519,0.760914 0.290528,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/30.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/30.png
new file mode 100644
index 0000000..f4ffb14
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/30.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/30.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/30.svg
new file mode 100644
index 0000000..434e663
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/30.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/31.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/31.png
new file mode 100644
index 0000000..0b29e87
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/31.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/31.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/31.svg
new file mode 100644
index 0000000..08c3f2d
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/31.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/32.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/32.png
new file mode 100644
index 0000000..a4740a3
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/32.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/32.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/32.svg
new file mode 100644
index 0000000..aa099c3
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/32.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/33.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/33.png
new file mode 100644
index 0000000..f23ccea
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/33.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/33.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/33.svg
new file mode 100644
index 0000000..fce979c
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/33.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/34.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/34.png
new file mode 100644
index 0000000..7e2ab31
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/34.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/34.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/34.svg
new file mode 100644
index 0000000..c67f8ec
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/34.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/35.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/35.png
new file mode 100644
index 0000000..02118e3
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/35.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/35.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/35.svg
new file mode 100644
index 0000000..da7780a
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/35.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/36.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/36.png
new file mode 100644
index 0000000..30f4fdf
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/36.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/36.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/36.svg
new file mode 100644
index 0000000..348549a
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/36.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/37.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/37.png
new file mode 100644
index 0000000..6174706
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/37.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/37.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/37.svg
new file mode 100644
index 0000000..7bc04d9
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/37.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/38.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/38.png
new file mode 100644
index 0000000..161661d
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/38.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/38.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/38.svg
new file mode 100644
index 0000000..ec2ad98
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/38.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/39.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/39.png
new file mode 100644
index 0000000..2d46b24
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/39.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/39.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/39.svg
new file mode 100644
index 0000000..664ffdd
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/39.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/4.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..9b9dd88
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/4.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/4.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..bc06c73
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/4.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 20.078077,19.493301 -1.460937,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460937,0 0,1.992187 m -3.959472,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09962,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.12175,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.025391,3.071289 2.75586,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/40.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/40.png
new file mode 100644
index 0000000..fe2a68f
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/40.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/40.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/40.svg
new file mode 100644
index 0000000..5a94d1b
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/40.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.440535,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.0136719,0 0,-1.784668 5.1547849,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.0253904,3.071289 2.7558594,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/5.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..f239fb6
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/5.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/5.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..82fb03d
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/5.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 16.035597,14.255508 c 0.520177,8e-6 1.004388,0.08025 1.452637,0.240723 0.448235,0.160489 0.838371,0.395678 1.17041,0.705566 0.332023,0.309903 0.592114,0.697272 0.780273,1.16211 0.188143,0.459315 0.282218,0.987797 0.282227,1.585449 -9e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.204761,0.520184 -0.506356,0.962892 -0.904785,1.328125 -0.398445,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261724,0.290528 -2.025391,0.290528 -0.304365,0 -0.60596,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863281,-0.124512 -0.271161,-0.04981 -0.531252,-0.116211 -0.780274,-0.199219 -0.24349,-0.08301 -0.464844,-0.17985 -0.664062,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672363,0.31543 0.254556,0.09408 0.517414,0.177086 0.788574,0.249024 0.276691,0.06641 0.553383,0.121746 0.830078,0.166015 0.27669,0.03874 0.539548,0.05811 0.788575,0.05811 0.741532,2e-6 1.305984,-0.152179 1.693359,-0.456543 0.387364,-0.309893 0.5810
49,-0.799639 0.581055,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751465,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320966,0.03874 -0.481445,0.06641 -0.154951,0.02768 -0.304365,0.05811 -0.448242,0.09131 -0.143883,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456542,-6.1840821 6.408204,0 0,2.1748051 -4.183594,0 -0.199219,2.382324 c 0.17708,-0.03873 0.381832,-0.07747 0.614258,-0.116211 0.237951,-0.03873 0.542313,-0.0581 0.913086,-0.05811"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/6.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..18866e6
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/6.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/6.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..e2f62af
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/6.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 11.702589,16.853653 c -10e-7,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.0664,-0.575514 0.179849,-1.126132 0.340332,-1.651856 0.166014,-0.531241 0.387368,-1.023753 0.664062,-1.477539 0.282225,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431638,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603186,-0.1936727 1.305984,-0.2905151 2.108399,-0.2905274 0.116204,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.138339,0.00555 0.276685,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251782,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210295,-0.04979 -0.434416,-0.08853 -0.672364,-0.116211 -0.232429,-0.03319 -0.467617,-0.04979 -0.705566,-0.0498 -0.747076,1e-5 -1.361334,0.09408 -1.842774,0.282226 -0.481449,0.182627 -0.863285,0.439951 -1.145507,0.771973 -0.28223,0.33204 -0.484216,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.215821,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243486,-0.384596 0.39843
7,-0.556153 0.160478,-0.177076 0.345862,-0.32649 0.556153,-0.448242 0.210282,-0.127271 0.44547,-0.22688 0.705566,-0.298828 0.26562,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419433,0.257324 0.420566,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.15494,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282226,1.768066 -0.182626,0.520184 -0.445484,0.962892 -0.788575,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643554,0.282227 -0.597661,0 -1.15658,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.973961,-0.542317 -1.361328,-0.979492 -0.381838,-0.437173 -0.683433,-0.987791 -0.904785,-1.651856 -0.215822,-0.669593 -0.323732,-1.460933 -0.323731,-2.374023 m 4.216797,3.270508 c 0.226883,2e-6 0.431635,-0.0415 0.614258,-0.124512 0.188145,-0.08854 0.348627,-0.218585 0.481445,-0.390137 0.13834,-0.17708 0.243483,-0.3
98434 0.31543,-0.664062 0.07747,-0.265622 0.116204,-0.581051 0.116211,-0.946289 -7e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243496,-0.343094 -0.617031,-0.514643 -1.120606,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.39014,0.229661 -0.53955,0.390137 -0.149418,0.160487 -0.265629,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.31543,0.755371 0.143876,0.221357 0.318193,0.401207 0.522949,0.539551 0.210282,0.138349 0.453772,0.207522 0.730469,0.20752"
+ id="path2846"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/7.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..52c3a18
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/7.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/7.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..a43460f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/7.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 12.789991,22.008438 4.316407,-9.960937 -5.578125,0 0,-2.1582035 8.367187,0 0,1.6103515 -4.424316,10.508789 -2.681153,0"
+ id="path2832"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/8.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..8a8cb21
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/8.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/8.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..2c82d3f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/8.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.761671,9.7149811 c 0.503576,1.23e-5 0.979487,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337558,0.243501 0.60595,0.547862 0.805176,0.913086 0.199211,0.365244 0.29882,0.794118 0.298828,1.286621 -8e-6,0.365243 -0.05535,0.697274 -0.166015,0.996094 -0.110686,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193693,0.237963 -0.423348,0.451017 -0.688965,0.639161 -0.265632,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.633619,0.362473 0.937988,0.572754 0.309888,0.210292 0.583814,0.448247 0.821777,0.713867 0.237948,0.260096 0.428866,0.55339 0.572754,0.879883 0.143872,0.326501 0.215812,0.691735 0.21582,1.095703 -8e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478686,0.758139 -0.838379,1.045898 -0.359707,0.287761 -0.791348,0.509115 -1.294921,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651856,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.9379
9,-0.362467 -1.286621,-0.639161 -0.348634,-0.276691 -0.614259,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265626,-0.857744 -0.265625,-1.361328 -10e-7,-0.415035 0.06087,-0.78857 0.182617,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498047,-0.896485 0.210285,-0.265619 0.456541,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271162,-0.171543 -0.525719,-0.356927 -0.763672,-0.556152 -0.237958,-0.204746 -0.445477,-0.428866 -0.622559,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -10e-7,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478677,-0.669585 0.821778,-0.913086 0.343096,-0.249012 0.738766,-0.434396 1.187011,-0.5561527 0.448239,-0.1217326 0.918616,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.107911,0.614258 0.07194,0.18262 0.17708,0.340334 0.315429,0.473145 0.143877,0.132814 0.32
096,0.237957 0.53125,0.315429 0.210283,0.07194 0.453772,0.107912 0.730469,0.10791 0.581049,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.43164,-1.087402 -6e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218593,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.320969,-0.307125 -0.514648,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 15.662062,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664063,0.398438 -0.199222,0.138351 -0.370772,0.293299 -0.514648,0.464844 -0.13835,0.16602 -0.24626,0.348637 -0.323731,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.701661,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514649,0.08301 -0.154952,0.05535 -0.290531,0.13559 -0.406738,0.240723 -0.110681,0.105153 -0.199223,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.31543
8 0.282226,0.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160478,0.09962 0.32926,0.199226 0.506348,0.298828 0.171545,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154943,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.12174,-0.138338 0.218582,-0.293286 0.290528,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.157721,-0.284984 -0.273926,-0.390137 -0.116217,-0.105133 -0.254563,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/9.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..0ae412f
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/9.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/9.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..b0f04c4
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/9.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.829054,15.052383 c -9e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340333,1.651856 -0.160489,0.525719 -0.381843,1.018232 -0.664062,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426113,0.332032 -0.940761,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.30046,0.282227 -2.108399,0.282227 -0.116214,0 -0.243492,-0.0028 -0.381836,-0.0083 -0.138348,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273927,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237954,0.02767 0.478676,0.04151 0.722168,0.0415 0.747067,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.481441,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.282221,-0.337562 0.481439,-0.738766 0.597657,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.107911,0 c -0.110683,0.199225 -0.243495,0.384609 -0.398437,0.556153 -0.
154954,0.171554 -0.337571,0.320968 -0.547852,0.448242 -0.210291,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.265629,0.07194 -0.56169,0.107914 -0.888183,0.10791 -0.52572,4e-6 -0.998864,-0.08577 -1.419434,-0.257324 -0.420575,-0.171545 -0.777508,-0.420568 -1.070801,-0.74707 -0.287761,-0.326492 -0.509115,-0.727696 -0.664062,-1.203614 -0.154949,-0.475904 -0.232423,-1.020988 -0.232422,-1.635253 -10e-7,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453774,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758135,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043127,-0.2905151 1.651855,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520176,0.210298 0.971184,0.534028 1.353027,0.971192 0.381829,0.437185 0.683423,0.990569 0.904786,1.660156 0.221345,0.669605 0.332022,1.458178 0.332031,2.365722 m -4.216797,-3.262207 c -0.226892,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188154,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132815,0.17155
9 -0.237959,0.392913 -0.315429,0.664062 -0.07194,0.265634 -0.107914,0.581063 -0.107911,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373536,1.394532 0.249019,0.343105 0.625321,0.514654 1.128906,0.514648 0.254552,6e-6 0.486974,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.53955,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124506,-0.401197 0.124512,-0.605958 -6e-6,-0.282218 -0.03598,-0.561677 -0.10791,-0.838378 -0.06641,-0.282218 -0.171556,-0.534008 -0.31543,-0.755372 -0.138352,-0.226878 -0.312668,-0.409495 -0.522949,-0.547851 -0.204758,-0.138336 -0.44548,-0.207509 -0.722168,-0.20752"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/bkgrnd_greydots.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/bkgrnd_greydots.png
new file mode 100644
index 0000000..2333a6d
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/bkgrnd_greydots.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/bullet_arrowblue.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/bullet_arrowblue.png
new file mode 100644
index 0000000..c235534
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/bullet_arrowblue.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/documentation.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/documentation.png
new file mode 100644
index 0000000..79d0a80
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/documentation.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/dot.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/dot.png
new file mode 100644
index 0000000..36a6859
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/dot.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/dot2.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/dot2.png
new file mode 100644
index 0000000..40aff92
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/dot2.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/green.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/green.png
new file mode 100644
index 0000000..ebb3c24
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/green.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/h1-bg.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/h1-bg.png
new file mode 100644
index 0000000..a2aad24
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/h1-bg.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/image_left.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/image_left.png
new file mode 100644
index 0000000..e8fe7a4
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/image_left.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/image_right.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/image_right.png
new file mode 100644
index 0000000..5b67443
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/image_right.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/important.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/important.png
new file mode 100644
index 0000000..f7594a3
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/important.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/important.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..2d33045
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/important.svg
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="important.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/important.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2611">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="681"
+ inkscape:window-width="738"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2613" />
+ </defs>
+ <g
+ transform="matrix(0.4626799,0,0,0.4626799,-5.2934127,-3.3160376)"
+ id="g5485">
+ <path
+ d="M 29.97756,91.885882 L 55.586992,80.409826 L 81.231619,91.807015 L 78.230933,63.90468 L 96.995009,43.037218 L 69.531053,37.26873 L 55.483259,12.974592 L 41.510292,37.311767 L 14.064204,43.164717 L 32.892392,63.97442 L 29.97756,91.885882 z"
+ id="path6799"
+ style="fill:#f3de82;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.536215,56.538729 L 55.48324,12.974601 L 41.51028,37.311813 L 55.536215,56.538729 z"
+ id="path6824"
+ style="opacity:0.91005291;fill:#f9f2cb;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 78.241135,63.937979 L 96.976198,43.044318 L 55.57947,56.614318 z"
+ id="use6833"
+ style="opacity:1;fill:#d0bc64;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 55.667994,80.684281 L 81.379011,91.931065 L 55.523838,56.869126 z"
+ id="use6835"
+ style="opacity:1;fill:#e0c656;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 13.877363,43.200977 L 32.640089,64.069652 L 55.283346,56.742618 z"
+ id="use6831"
+ style="opacity:1;fill:#d1ba59;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 55.32792,80.684281 L 29.616903,91.931065 L 55.472076,56.869126 z"
+ id="use6837"
+ style="opacity:1;fill:#d2b951;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 96.976198,43.044318 L 69.504294,37.314027 L 55.57947,56.614318 z"
+ id="path7073"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 81.379011,91.931065 L 78.214821,64.046881 L 55.523838,56.869126 z"
+ id="path7075"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 41.341708,37.434209 L 13.877363,43.200977 L 55.283346,56.742618 z"
+ id="path7077"
+ style="opacity:1;fill:#f6e59d;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 29.616903,91.931065 L 32.781093,64.046881 L 55.472076,56.869126 z"
+ id="path7079"
+ style="opacity:1;fill:#f3df8b;fill-opacity:1;enable-background:new" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/logo.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/logo.png
new file mode 100644
index 0000000..66a3104
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/logo.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/note.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/note.png
new file mode 100644
index 0000000..d6c4518
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/note.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/note.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..70e43b6
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/note.svg
@@ -0,0 +1,111 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="note.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/note.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata16">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="1024"
+ inkscape:window-width="1205"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="22.217181"
+ inkscape:cy="20"
+ inkscape:window-x="334"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective18" />
+ </defs>
+ <g
+ transform="matrix(0.468275,0,0,0.468275,-5.7626904,-7.4142703)"
+ id="layer1">
+ <g
+ transform="matrix(0.115136,0,0,0.115136,9.7283,21.77356)"
+ id="g8014"
+ style="enable-background:new">
+ <g
+ id="g8518"
+ style="opacity:1">
+ <path
+ d="M -2512.4524,56.33197 L 3090.4719,56.33197 L 3090.4719,4607.3813 L -2512.4524,4607.3813 L -2512.4524,56.33197 z"
+ transform="matrix(0.1104659,-2.3734892e-2,2.2163258e-2,0.1031513,308.46782,74.820675)"
+ id="rect8018"
+ style="fill:#ffe680;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ <g
+ transform="matrix(0.5141653,-7.1944682e-2,7.1944682e-2,0.5141653,146.04015,-82.639785)"
+ id="g8020">
+ <path
+ d="M 511.14114,441.25315 C 527.3248,533.52772 464.31248,622.82928 370.39916,640.71378 C 276.48584,658.59828 187.23462,598.29322 171.05095,506.01865 C 154.86728,413.74408 217.8796,324.44253 311.79292,306.55803 C 405.70624,288.67353 494.95747,348.97858 511.14114,441.25315 z"
+ id="path8022"
+ style="opacity:1;fill:#e0c96f;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(1.2585415,-0.2300055,0.2168789,1.1867072,-248.76141,68.254424)"
+ id="path8024"
+ style="opacity:1;fill:#c00000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 358.5625,281.15625 C 348.09597,281.05155 337.43773,281.94729 326.71875,283.90625 C 240.96686,299.57789 183.37901,377.92385 198.15625,458.78125 C 209.70749,521.98673 262.12957,567.92122 325.40625,577.5625 L 357.25,433.6875 L 509.34375,405.875 C 509.14405,404.58166 509.0804,403.29487 508.84375,402 C 495.91366,331.24978 431.82821,281.88918 358.5625,281.15625 z"
+ id="path8026"
+ style="opacity:1;fill:#b60000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 294.2107,361.9442 L 282.79367,370.38482 L 261.73414,386.13346 C 253.13706,404.40842 254.3359,423.7989 259.7176,444.39774 C 273.6797,497.83861 313.42636,523.96124 369.50989,517.58957 C 398.21848,514.32797 424.51832,504.67345 440.64696,484.15958 L 469.89512,447.48298 L 294.2107,361.9442 z"
+ id="path8028"
+ style="fill:#750000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.09999999;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-78.013985,79.234385)"
+ id="path8030"
+ style="opacity:1;fill:#d40000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-69.306684,71.273294)"
+ id="path8032"
+ style="opacity:1;fill:#e11212;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/red.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/red.png
new file mode 100644
index 0000000..d32d5e2
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/red.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/shade.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/shade.png
new file mode 100644
index 0000000..a73afdf
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/shade.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/shine.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/shine.png
new file mode 100644
index 0000000..a18f7c4
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/shine.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/stock-go-back.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/stock-go-back.png
new file mode 100644
index 0000000..d320f26
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/stock-go-back.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/stock-go-forward.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/stock-go-forward.png
new file mode 100644
index 0000000..1ee5a29
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/stock-go-forward.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/stock-go-up.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/stock-go-up.png
new file mode 100644
index 0000000..1cd7332
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/stock-go-up.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/stock-home.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/stock-home.png
new file mode 100644
index 0000000..122536d
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/stock-home.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/title_logo.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/title_logo.png
new file mode 100644
index 0000000..d5182b4
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/title_logo.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/title_logo.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/title_logo.svg
new file mode 100644
index 0000000..e8fd52b
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/title_logo.svg
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="220"
+ height="70"
+ id="svg6180">
+ <defs
+ id="defs6182" />
+ <g
+ transform="translate(-266.55899,-345.34488)"
+ id="layer1">
+ <path
+ d="m 316.7736,397.581 c 0,0 0,0 -20.53889,0 0.3327,4.45245 3.92157,7.77609 8.70715,7.77609 3.38983,0 6.31456,-1.39616 8.64094,-3.65507 0.46553,-0.46679 0.99726,-0.59962 1.59519,-0.59962 0.79781,0 1.59561,0.39932 2.12692,1.06388 0.3327,0.46553 0.53216,0.99726 0.53216,1.52857 0,0.73118 -0.3327,1.52857 -0.93106,2.12734 -2.7919,2.99052 -7.51086,4.98503 -12.16403,4.98503 -8.44149,0 -15.22074,-6.77967 -15.22074,-15.22158 0,-8.44149 6.58022,-15.22074 15.02171,-15.22074 8.37529,0 14.62323,6.51317 14.62323,15.08749 0,1.26418 -1.12924,2.12861 -2.39258,2.12861 z m -12.23065,-11.76512 c -4.45329,0 -7.51085,2.92473 -8.17499,7.17731 10.03626,0 16.35083,0 16.35083,0 -0.59836,-4.05355 -3.78874,-7.17731 -8.17584,-7.17731 z"
+ id="path11"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 375.46344,410.80807 c -8.44106,0 -15.22074,-6.77968 -15.22074,-15.22159 0,-8.44149 6.77968,-15.22074 15.22074,-15.22074 8.44234,0 15.22159,6.77925 15.22159,15.22074 -4.2e-4,8.44149 -6.77968,15.22159 -15.22159,15.22159 z m 0,-24.65992 c -5.31688,0 -8.77377,4.25427 -8.77377,9.43833 0,5.18364 3.45689,9.43833 8.77377,9.43833 5.31731,0 8.77504,-4.25469 8.77504,-9.43833 -4.2e-4,-5.18406 -3.45773,-9.43833 -8.77504,-9.43833 z"
+ id="path13"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 412.66183,380.36574 c -4.45963,0 -7.40966,1.319 -10.01391,4.62956 l -0.24036,-1.53995 0,0 c -0.20198,-1.60743 -1.57326,-2.84926 -3.23382,-2.84926 -1.80139,0 -3.26206,1.459 -3.26206,3.26081 0,0.003 0,0.005 0,0.008 l 0,0 0,0.003 0,0 0,23.40712 c 0,1.79464 1.46194,3.25743 3.257,3.25743 1.79465,0 3.25744,-1.46279 3.25744,-3.25743 l 0,-12.56209 c 0,-5.71621 4.98502,-8.57432 10.23613,-8.57432 1.59519,0 2.85726,-1.32953 2.85726,-2.92515 0,-1.59561 -1.26207,-2.85726 -2.85768,-2.85726 z"
+ id="path15"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 447.02614,395.58648 c 0.0666,-8.17541 -5.78326,-15.22074 -15.222,-15.22074 -8.44192,0 -15.28779,6.77925 -15.28779,15.22074 0,8.44191 6.64684,15.22159 14.68985,15.22159 4.01434,0 7.62682,-2.06621 9.23846,-4.22518 l 0.79359,2.01434 0,0 c 0.42589,1.13177 1.5176,1.93717 2.7978,1.93717 1.65001,0 2.98756,-1.33671 2.99009,-2.98545 l 0,0 0,-7.80687 0,0 0,-4.1556 z m -15.222,9.43833 c -5.31773,0 -8.77419,-4.25469 -8.77419,-9.43833 0,-5.18406 3.45604,-9.43833 8.77419,-9.43833 5.3173,0 8.77419,4.25427 8.77419,9.43833 0,5.18364 -3.45689,9.43833 -8.77419,9.43833 z"
+ id="path17"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 355.01479,368.3337 c 0,-1.7938 -1.46194,-3.18997 -3.25659,-3.18997 -1.79422,0 -3.25743,1.39659 -3.25743,3.18997 l 0,17.1499 c -1.66097,-3.05756 -5.25026,-5.11786 -9.50495,-5.11786 -8.64052,0 -14.42336,6.51318 -14.42336,15.22074 0,8.70757 5.98229,15.22159 14.42336,15.22159 3.76555,0 7.03057,-1.55429 8.98587,-4.25554 l 0.72317,1.83428 c 0.44782,1.25912 1.64917,2.16024 3.06051,2.16024 1.78621,0 3.24984,-1.45435 3.24984,-3.24815 0,-0.005 0,-0.009 0,-0.0139 l 0,0 0,-38.95128 -4.2e-4,0 z m -15.22116,36.69111 c -5.31731,0 -8.70715,-4.25469 -8.70715,-9.43833 0,-5.18406 3.38984,-9.43833 8.70715,-9.43833 5.31773,0 8.70714,4.0544 8.70714,9.43833 0,5.38309 -3.38941,9.43833 -8.70714,9.43833 z"
+ id="path19"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 287.21553,365.34023 c -0.59414,-0.0877 -1.19966,-0.13198 -1.80097,-0.13198 -6.73118,0 -12.20746,5.4767 -12.20746,12.20788 l 0,3.8132 -3.98903,0 c -1.46237,0 -2.65908,1.19671 -2.65908,2.65781 0,1.46321 1.19671,2.93738 2.65908,2.93738 l 3.98819,0 0,20.46004 c 0,1.79464 1.46236,3.25743 3.25658,3.25743 1.79507,0 3.25744,-1.46279 3.25744,-3.25743 l 0,-20.46004 4.40986,0 c 1.46194,0 2.65823,-1.47417 2.65823,-2.93738 0,-1.46152 -1.19629,-2.65823 -2.65823,-2.65823 l -4.40733,0 0,-3.8132 c 0,-3.13852 2.55323,-6.11469 5.69175,-6.11469 0.28294,0 0.56757,0.0211 0.84672,0.062 1.78031,0.26355 3.4358,-0.54269 3.70019,-2.32342 0.2627,-1.77904 -0.96606,-3.43538 -2.74594,-3.69935 z"
+ id="path21"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 482.01243,363.57426 c 0,-10.06788 -8.16108,-18.22938 -18.22897,-18.22938 -10.06282,0 -18.22179,8.15475 -18.22854,18.21631 l -4.2e-4,-4.2e-4 0,14.1071 4.2e-4,4.2e-4 c 0.005,2.28463 1.85832,4.13409 4.14463,4.13409 0.007,0 0.0127,-8.4e-4 0.0194,-8.4e-4 l 0.001,8.4e-4 14.07083,0 0,0 c 10.06409,-0.004 18.22138,-8.16276 18.22138,-18.22812 z"
+ id="path25"
+ style="fill:#294172" />
+ <path
+ d="m 469.13577,349.66577 c -4.72528,0 -8.55576,3.83049 -8.55576,8.55577 0,0.002 0,0.004 0,0.006 l 0,4.52836 -4.51444,0 c -8.5e-4,0 -8.5e-4,0 -0.001,0 -4.72528,0 -8.55576,3.81193 -8.55576,8.53678 0,4.72528 3.83048,8.55577 8.55576,8.55577 4.72486,0 8.55534,-3.83049 8.55534,-8.55577 0,-0.002 0,-0.004 0,-0.006 l 0,-4.54733 4.51444,0 c 8.5e-4,0 0.001,0 0.002,0 4.72486,0 8.55534,-3.79296 8.55534,-8.51781 0,-4.72528 -3.83048,-8.55577 -8.55534,-8.55577 z m -8.55576,21.63483 c -0.004,2.48998 -2.02446,4.50811 -4.51571,4.50811 -2.49378,0 -4.53426,-2.02193 -4.53426,-4.5157 0,-2.49421 2.04048,-4.55366 4.53426,-4.55366 0.002,0 0.004,4.2e-4 0.006,4.2e-4 l 3.86971,0 c 0.001,0 0.002,-4.2e-4 0.003,-4.2e-4 0.35209,0 0.63799,0.28505 0.63799,0.63715 0,4.2e-4 -4.2e-4,8.4e-4 -4.2e-4,0.001 l 0,3.92284 -4.2e-4,0 z m 8.55534,-8.5448 c -0.001,0 -0.003,0 -0.004,0 l -3.87223,0 c -8.4e-4,0 -0.002,0 -0.002,0 -0.35252,0 -0.63757,-0.28506 -0.63757,-0.63758 l 0,-4.2e-4 0,-3.90343 c 0.004,-2.49083 2.02
446,-4.50854 4.51571,-4.50854 2.49378,0 4.53468,2.02193 4.53468,4.51613 4.2e-4,2.49336 -2.04048,4.53384 -4.53426,4.53384 z"
+ id="path29"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 460.58001,362.7558 0,-4.52836 c 0,-0.002 0,-0.004 0,-0.006 0,-4.72528 3.83048,-8.55577 8.55576,-8.55577 0.71685,0 1.22623,0.0805 1.88952,0.25469 0.96774,0.25385 1.75796,1.04618 1.75838,1.96922 4.2e-4,1.11575 -0.80919,1.92621 -2.0194,1.92621 -0.57642,0 -0.78473,-0.11048 -1.62892,-0.11048 -2.49125,0 -4.51149,2.01771 -4.51571,4.50854 l 0,3.90385 0,4.2e-4 c 0,0.35252 0.28505,0.63758 0.63757,0.63758 4.3e-4,0 0.001,0 0.002,0 l 2.96521,0 c 1.10521,0 1.99747,0.88467 1.99832,1.99283 0,1.10816 -0.89353,1.99114 -1.99832,1.99114 l -3.60489,0 0,4.54733 c 0,0.002 0,0.004 0,0.006 0,4.72485 -3.83048,8.55534 -8.55534,8.55534 -0.71684,0 -1.22623,-0.0805 -1.88952,-0.25469 -0.96774,-0.25343 -1.75838,-1.04618 -1.7588,-1.9688 0,-1.11575 0.80919,-1.92663 2.01982,-1.92663 0.576,0 0.78473,0.11048 1.6285,0.11048 2.49125,0 4.51191,-2.01771 4.51613,-4.50811 0,0 0,-3.92368 0,-3.9241 0,-0.35168 -0.2859,-0.63673 -0.63799,-0.63673 -4.3e-4,0 -8.5e-4,0 -0.002,0 l -2.96521,-4.2e-4 c -1.10521,0 -1.
99831,-0.88214 -1.99831,-1.9903 -4.3e-4,-1.11533 0.90238,-1.99367 2.01939,-1.99367 l 3.58339,0 0,0 z"
+ id="path31"
+ style="fill:#ffffff" />
+ <path
+ d="m 477.41661,378.55292 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0 0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496 0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279 0,2.9226 -0.43694,0 0,-3.32833"
+ id="text6223"
+ style="fill:#294172;enable-background:new" />
+ </g>
+ <path
+ d="m 181.98344,61.675273 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0 0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496 0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279 0,2.9226 -0.43694,0 0,-3.32833"
+ id="path2391"
+ style="fill:#294172;enable-background:new" />
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/warning.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/warning.png
new file mode 100644
index 0000000..ce09951
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/warning.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/warning.svg b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..5f2612c
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/warning.svg
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="warning.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/warning.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2482">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="910"
+ inkscape:window-width="1284"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2484" />
+ </defs>
+ <g
+ transform="matrix(0.4536635,0,0,0.4536635,-5.1836431,-4.6889387)"
+ id="layer1">
+ <g
+ transform="translate(2745.6887,-1555.5977)"
+ id="g8304"
+ style="enable-background:new">
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.8233528,8.9983906e-3,-8.9983906e-3,0.8233528,-1398.5561,740.7914)"
+ id="path8034"
+ style="opacity:1;fill:#efd259;fill-opacity:1;stroke:#efd259;stroke-opacity:1" />
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.6467652,7.0684723e-3,-7.0684723e-3,0.6467652,-1675.7492,927.16391)"
+ id="path8036"
+ style="opacity:1;fill:#a42324;fill-opacity:1;stroke:#a42324;stroke-opacity:1" />
+ <path
+ d="M -2686.7886,1597.753 C -2686.627,1596.5292 -2686.5462,1595.6987 -2686.5462,1595.218 C -2686.5462,1593.1637 -2688.0814,1592.0711 -2690.9899,1592.0711 C -2693.8985,1592.0711 -2695.4336,1593.12 -2695.4336,1595.218 C -2695.4336,1595.961 -2695.3528,1596.7914 -2695.1912,1597.753 L -2692.929,1614.4491 L -2689.0508,1614.4491 L -2686.7886,1597.753"
+ id="path8038"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ <path
+ d="M -2690.9899,1617.8197 C -2693.6124,1617.8197 -2695.8118,1619.9346 -2695.8118,1622.6416 C -2695.8118,1625.3486 -2693.6124,1627.4635 -2690.9899,1627.4635 C -2688.2829,1627.4635 -2686.168,1625.264 -2686.168,1622.6416 C -2686.168,1619.9346 -2688.2829,1617.8197 -2690.9899,1617.8197"
+ id="path8040"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/watermark-draft.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/watermark-draft.png
new file mode 100644
index 0000000..0ead5af
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/watermark-draft.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/yellow.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/yellow.png
new file mode 100644
index 0000000..223865d
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/Common_Content/images/yellow.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/images/Editing-Bridge-Connection-1_Gnome3.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/images/Editing-Bridge-Connection-1_Gnome3.png
new file mode 100644
index 0000000..77b5101
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/images/Editing-Bridge-Connection-1_Gnome3.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/images/Network-Details-Wired_Gnome3.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/images/Network-Details-Wired_Gnome3.png
new file mode 100644
index 0000000..ba58a95
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/images/Network-Details-Wired_Gnome3.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/images/Network-Wired_Gnome3.png b/public_html/en-US/Fedora/21/html-single/Networking_Guide/images/Network-Wired_Gnome3.png
new file mode 100644
index 0000000..56fca9c
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/Networking_Guide/images/Network-Wired_Gnome3.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/Networking_Guide/index.html b/public_html/en-US/Fedora/21/html-single/Networking_Guide/index.html
new file mode 100644
index 0000000..b528f6f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html-single/Networking_Guide/index.html
@@ -0,0 +1,4752 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Networking Guide</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><meta name="description" content="The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guid
e to form the foundation for this book." /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><div xml:lang="en-US" class="book" id="idm225438044560" lang="en-US"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">21</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="idm225438044560" class="title">Networking Guide
</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">Configuration and Administration of networking for Fedora 20</h2></div><p class="edition">Edition 2</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+ <span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> </object></span>
+
+ </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="en-US" class="authorgroup" lang="en-US"><div class="author"><h3 class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:swadeley at redhat.com">swadeley at redhat.com</a></code></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="idm225436531376" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2014 Red Hat, Inc. and others.
+ </div><div class="para">
+ The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
+ </div><div class="para">
+ Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
+ </div><div class="para">
+ Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
+ </div><div class="para">
+ For guidelines on the permitted uses of the Fedora trademarks, refer to <a href="https://fedoraproject.org/wiki/Legal:Trademark_guidelines">https://fedoraproject.org/wiki/Legal:Trademark_guidelines</a>.
+ </div><div class="para">
+ <span class="trademark">Linux</span>® is the registered trademark of Linus Torvalds in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Java</span>® is a registered trademark of Oracle and/or its affiliates.
+ </div><div class="para">
+ <span class="trademark">XFS</span>® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
+ </div><div class="para">
+ <span class="trademark">MySQL</span>® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
+ </div><div class="para">
+ All other trademarks are the property of their respective owners.
+ </div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract"><h6>Abstract</h6><div class="para">
+ The <em class="citetitle">Networking Guide</em> documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking.
+ </div><div class="para">
+ This book is based on the <em class="citetitle">Deployment Guide</em> from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.
+ </div></div></div></div><hr /></div><div class="toc"><dl class="toc"><dt><span class="preface"><a href="#idm225414215520">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Preface-Target_Audience">1. Target Audience</a></span></dt><dt><span class="section"><a href="#sec-Preface-About_this_book">2. About This Book</a></span></dt><dt><span class="section"><a href="#sec-Whats-New">3. What's new in Fedora 20</a></span></dt><dt><span class="section"><a href="#sec-Preface-Book_Organization">4. How to Read this Book</a></span></dt><dt><span class="section"><a href="#idm225432817136">5. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225430776128">5.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="#idm225446127760">5.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="#idm225463597984">5.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-P
reface-Feedback">6. Feedback</a></span></dt><dt><span class="section"><a href="#pref-Acknowledgments">7. Acknowledgments</a></span></dt></dl></dd><dt><span class="part"><a href="#part-Networking">I. Networking</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-Introduction_to_Fedora_Networking">1. Introduction to Fedora Networking</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-How_this_Book_is_Structured">1.1. How this Book is Structured</a></span></dt><dt><span class="section"><a href="#sec-Introduction_to_NetworkManager">1.2. Introduction to NetworkManager</a></span></dt><dt><span class="section"><a href="#sec-Installing_NetworkManager">1.3. Installing NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-The_NetworkManager_Daemon">1.3.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="#sec-Interacting_with_NetworkManager">1.3.2. Interacting with NetworkManager</a></span></dt></dl></dd><dt><span
class="section"><a href="#sec-Network_Config_Using_CLI">1.4. Network Configuration Using the Command Line Interface (CLI)</a></span></dt><dt><span class="section"><a href="#sec-Network_Config_Using_nmcli">1.5. Network Configuration Using NetworkManager's CLI (nmcli)</a></span></dt><dt><span class="section"><a href="#sec-NetworkManager_and_the_Network_Scripts">1.6. NetworkManager and the Network Scripts</a></span></dt><dt><span class="section"><a href="#sec-Network_Configuration_Using_sysconfig_Files">1.7. Network Configuration Using sysconfig Files</a></span></dt><dt><span class="section"><a href="#sec-Introduction_to_Fedora_Networking-additional_resources">1.8. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Introduction_to_Fedora_Networking-docs-inst">1.8.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configure_Networking">2. Configure Networking</a></span></dt><dd><dl><dt><span clas
s="section"><a href="#sec-Static_and_Dynamic_Interface_Settings">2.1. Static and Dynamic Interface Settings</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-When_to_Use_Static_Network_Interface_Settings">2.1.1. When to Use Static Network Interface Settings</a></span></dt><dt><span class="section"><a href="#sec-When_to_Use_Dynamic_Interface_Settings">2.1.2. When to Use Dynamic Interface Settings</a></span></dt><dt><span class="section"><a href="#sec-Selecting_Network_Configuration_Methods">2.1.3. Selecting Network Configuration Methods</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface">2.2. Using NetworkManager with the GNOME Graphical User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Connecting_to_a_Network_Using_a_GUI">2.2.1. Connecting to a Network Using a GUI</a></span></dt><dt><span class="section"><a href="#sec-Configuring_New_and_Editing_Existing_Connec
tions">2.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="#sec-Connecting_to_a_Network_Automatically">2.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="#sec-System-wide_and_Private_Connection_Profiles">2.2.4. System-wide and Private Connection Profiles</a></span></dt><dt><span class="section"><a href="#sec-Configuring_a_Wired_Ethernet_Connection">2.2.5. Configuring a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="#sec-Configuring_a_Wi-Fi_Connection">2.2.6. Configuring a Wi-Fi Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_VPN_Connection">2.2.7. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_Mobile_Broadband_Connection">2.2.8. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_DSL_Connection">2.2.9. E
stablishing a DSL Connection</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Connection_Settings">2.2.10. Configuring Connection Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_the_Command_Line_Interface">2.3. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configuring_a_Network_Interface_Using_ifcg_Files">2.3.1. Configuring a Network Interface Using ifcfg Files</a></span></dt><dt><span class="section"><a href="#sec-Configuring_a_Network_Interface_Using_ip_commands">2.3.2. Configuring a Network Interface Using ip Commands</a></span></dt><dt><span class="section"><a href="#sec-Static-Routes_and_the_Default_Gateway">2.3.3. Static Routes and the Default Gateway</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Static_Routes_in_ifcfg_files">2.3.4. Configuring Static Routes in ifcfg files</a></span></dt><dt><span class="section"><a href="#sec-Configuring_IPv6_
Tokenized_Interface_Identifiers">2.3.5. Configuring IPv6 Tokenized Interface Identifiers</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_the_NetworkManager_Command_Line_Tool_nmcli">2.4. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Understanding_the_nmcli_Options">2.4.1. Understanding the nmcli Options</a></span></dt><dt><span class="section"><a href="#sec-Connecting_to_a_Network_Using_nmcli">2.4.2. Connecting to a Network Using nmcli</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Static_Routes_Using_nmcli">2.4.3. Configuring Static Routes Using nmcli</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_Networking-additional_resources">2.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configure_Networking-docs-inst">2.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-Config
ure_Networking_Online_Documentation">2.5.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configure_Host_Names">3. Configure Host Names</a></span></dt><dd><dl><dt><span class="section"><a href="#sec_Understanding_Host_Names">3.1. Understanding Host Names</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Recommended_Naming_Practices">3.1.1. Recommended Naming Practices</a></span></dt></dl></dd><dt><span class="section"><a href="#sec_Configuring_Host_Names_Using_hostnamectl">3.2. Configuring Host Names Using hostnamectl</a></span></dt><dd><dl><dt><span class="section"><a href="#sec_View_All_the_Host_Names">3.2.1. View All the Host Names</a></span></dt><dt><span class="section"><a href="#sec_Set_All_the_Host_Names">3.2.2. Set All the Host Names</a></span></dt><dt><span class="section"><a href="#sec_Set_a_Particular_Host_Name">3.2.3. Set a Particular Host Name</a></span></dt><dt><span class="section"><a href="#sec_Cle
ar_a_Particular_Host_Name">3.2.4. Clear a Particular Host Name</a></span></dt><dt><span class="section"><a href="#sec_Changing_Host_Names_Remotely">3.2.5. Changing Host Names Remotely</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Host_Names_Using_nmcli">3.3. Configuring Host Names Using nmcli</a></span></dt><dt><span class="section"><a href="#sec-additional_resources">3.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-hostnamectl-docs-inst">3.4.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-hostnamectl-Online_Documentation">3.4.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configure_Network_Bonding">4. Configure Network Bonding</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Bond-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces">4.1. Understanding the Default Behavior of Master and Slave In
terfaces</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Bond_Connection_Using_a_GUI">4.2. Creating a Bond Connection Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_Bond_Connection">4.2.1. Establishing a Bond Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Network_Bonding_Using_the_Command_Line_Interface">4.3. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Check_if_Bonding_Kernel_Module_is_Installed">4.3.1. Check if Bonding Kernel Module is Installed</a></span></dt><dt><span class="section"><a href="#sec-Create_a_Channel_Bonding_Interface">4.3.2. Create a Channel Bonding Interface</a></span></dt><dt><span class="section"><a href="#sec-Creating_SLAVE_Interfaces">4.3.3. Creating SLAVE Interfaces</a></span></dt><dt><span class="section"><a href="#sec-Activating_a_Channel_Bond">4.3.4. Activating a Channel Bond</a></span></dt><dt><span cl
ass="section"><a href="#sec-Creating_Multiple_Bonds">4.3.5. Creating Multiple Bonds</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_Channel_Bonding">4.4. Using Channel Bonding</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-modules-bonding-directives">4.4.1. Bonding Module Directives</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli">4.5. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="#sec-Configure_Network_Bonding-additional_resources">4.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configure_Network_Bonding-docs-inst">4.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-Configure_Network_Bonding_Online_Documentation">4.6.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configure_Networ
k_Teaming">5. Configure Network Teaming</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Understanding_Network_Teaming">5.1. Understanding Network Teaming</a></span></dt><dt><span class="section"><a href="#sec-Comparison_of_Network_Teaming_to_Bonding">5.2. Comparison of Network Teaming to Bonding</a></span></dt><dt><span class="section"><a href="#sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces">5.3. Understanding the Default Behavior of Master and Slave Interfaces</a></span></dt><dt><span class="section"><a href="#sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners">5.4. Understanding the Network Teaming Daemon and the "Runners"</a></span></dt><dt><span class="section"><a href="#sec-Install_the_Network_Teaming_Daemon">5.5. Install the Network Teaming Daemon</a></span></dt><dt><span class="section"><a href="#sec-Converting_a_Bond_to_a_Team">5.6. Converting a Bond to a Team</a></span></dt><dt><span class="section"><a href="#sec
-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team">5.7. Selecting Interfaces to Use as Ports for a Network Team</a></span></dt><dt><span class="section"><a href="#sec-Selecting_Network_Team_Configuration_Methods">5.8. Selecting Network Team Configuration Methods</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Network_Team_Using_a_GUI">5.9. Creating a Network Team Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_Team_Connection">5.9.1. Establishing a Team Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_a_Network_Team_Using-the_Command_Line">5.10. Configure a Network Team Using the Command Line</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Creating_a_Network_Team_Using_teamd">5.10.1. Creating a Network Team Using teamd</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Network_Team_Using_ifcfg_Files">5.10.2. Creating a Network Team Using ifcfg
Files</a></span></dt><dt><span class="section"><a href="#sec-Add_a_port_to_a_Network_Team_Using_iputils">5.10.3. Add a Port to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="#sec-Listing_the_ports_of_a_Team_Using_teamnl">5.10.4. Listing the ports of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Options_of_a_Team_Using_teamnl">5.10.5. Configuring Options of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="#sec-Add_an_address_to_a_Network_Team_Using_iputils">5.10.6. Add an Address to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="#sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils">5.10.7. Bring up an Interface to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="#sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl">5.10.8. Viewing the Active Port Options of a Team Using teamnl</a></span></dt><dt><span class="section"
><a href="#sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl">5.10.9. Setting the Active Port Options of a Team Using teamnl</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Controlling_teamd_with_teamdctl">5.11. Controlling teamd with teamdctl</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Add_a_port_to_a_Network_Team">5.11.1. Add a Port to a Network Team</a></span></dt><dt><span class="section"><a href="#sec-Remove_a_Port_From_a_Network_Team">5.11.2. Remove a Port From a Network Team</a></span></dt><dt><span class="section"><a href="#sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team">5.11.3. Apply a Configuration to a Port in a Network Team</a></span></dt><dt><span class="section"><a href="#sec-View_the_Configuration_of_a_Port_in_a_Network_Team">5.11.4. View the Configuration of a Port in a Network Team</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_teamd_Runners">5.12. Configure teamd Runners</a></span></dt
><dd><dl><dt><span class="section"><a href="#sec-Configure_the_broadcast_Runner">5.12.1. Configure the broadcast Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_the_random_Runner">5.12.2. Configure the random Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_the_roundrobin_Runner">5.12.3. Configure the roundrobin Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_the_activebackup_Runner">5.12.4. Configure the activebackup Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_the_loadbalance_Runner">5.12.5. Configure the loadbalance Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_the_LACP_Runner">5.12.6. Configure the LACP (802.3ad) Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_Monitoring_of_the_Link_State">5.12.7. Configure Monitoring of the Link State</a></span></dt><dt><span class="section"><a href="#sec-Configure_Port_Selection_Override">5
.12.8. Configure Port Selection Override</a></span></dt><dt><span class="section"><a href="#sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm">5.12.9. Configure BPF-based Tx Port Selectors</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_Network_Teaming_Using_nmcli">5.13. Configure Network Teaming Using nmcli</a></span></dt><dt><span class="section"><a href="#sec-Network_Teaming-additional_resources">5.14. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-teamd-docs-inst">5.14.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-teamd_docs-online">5.14.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configure_Network_Bridging">6. Configure Network Bridging</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configure_Network_Bridging_Using_a_GUI">6.1. Configure Network Bridging Using a GUI</a></span></dt>
<dd><dl><dt><span class="section"><a href="#sec-Establishing_a_Bridge_Connection">6.1.1. Establishing a Bridge Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Network_Bridging_Using_the_Command_Line_Interface">6.2. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Check_if_Bridging_Kernel_Module_is_Installed">6.2.1. Check if Bridging Kernel Module is Installed</a></span></dt><dt><span class="section"><a href="#sec-Create_a_Network_Bridge">6.2.2. Create a Network Bridge</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli">6.3. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="#sec-Network_Bridging-additional_resources">6.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Network_Bridging-docs-inst">6.4.1. Installed Documentation</a
></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configure_802_1Q_VLAN_Tagging">7. Configure 802.1Q VLAN tagging</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Selecting_VLAN_Interface_Configuration_Methods">7.1. Selecting VLAN Interface Configuration Methods</a></span></dt><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI">7.2. Configure 802.1Q VLAN Tagging Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_VLAN_Connection">7.2.1. Establishing a VLAN Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line">7.3. Configure 802.1Q VLAN Tagging Using the Command Line</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_Up_802.1Q_VLAN_Tagging_Using_ifcfg_Files">7.3.1. Setting Up 802.1Q VLAN Tagging Using ifcfg Files</a></span></dt><dt><span class="section"><a href="#sec-Configure_8
02_1Q_VLAN_Tagging_ip_Commands">7.3.2. Configure 802.1Q VLAN Tagging Using ip Commands</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli">7.4. Configure 802.1Q VLAN Tagging Using the Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging-additional_resources">7.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging-docs-inst">7.5.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Consistent_Network_Device_Naming">8. Consistent Network Device Naming</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Naming_Schemes_Hierarchy">8.1. Naming Schemes Hierarchy</a></span></dt><dt><span class="section"><a href="#sec-Understanding_the_Device_Renaming_Procedure">8.2. Understanding the Device Renaming Procedure</a></span></dt><dt><sp
an class="section"><a href="#sec-Understanding_the_Predictable_Network_Interface_Device_Names">8.3. Understanding the Predictable Network Interface Device Names</a></span></dt><dt><span class="section"><a href="#sec-Naming_Scheme_for_Network_Devices_Available_for_Linux_on_System_z">8.4. Naming Scheme for Network Devices Available for Linux on System z</a></span></dt><dt><span class="section"><a href="#sec-Naming_Scheme_for_VLAN_Interfaces">8.5. Naming Scheme for VLAN Interfaces</a></span></dt><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming_Using_biosdevname">8.6. Consistent Network Device Naming Using biosdevname</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming-System_Requirements">8.6.1. System Requirements</a></span></dt><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming-Enabling_and_Disabling">8.6.2. Enabling and Disabling the Feature</a></span></dt></dl></dd><dt><span class="sec
tion"><a href="#sec-Consistent_Network_Device_Naming-Notes">8.7. Notes for Administrators</a></span></dt><dt><span class="section"><a href="#sec-Controlling_the_Selection_of_Network_Device_Names">8.8. Controlling the Selection of Network Device Names</a></span></dt><dt><span class="section"><a href="#sec-Disabling_Consistent_Network_Device_Naming">8.9. Disabling Consistent Network Device Naming</a></span></dt><dt><span class="section"><a href="#sec_Troubleshooting_Network_Device_Naming">8.10. Troubleshooting Network Device Naming</a></span></dt><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming-additional_resources">8.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming-docs-inst">8.11.1. Installed Documentation</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="#part-Servers">II. Servers</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-DHCP_Server
s">9. DHCP Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-dhcp-why">9.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="#sec-dhcp-configuring-server">9.2. Configuring a DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#config-file">9.2.1. Configuration File</a></span></dt><dt><span class="section"><a href="#lease-database">9.2.2. Lease Database</a></span></dt><dt><span class="section"><a href="#idm225408573744">9.2.3. Starting and Stopping the Server</a></span></dt></dl></dd><dt><span class="section"><a href="#dhcp-relay-agent">9.3. DHCP Relay Agent</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configure_dhcrelay_as_a_DHCPv4_and_BOOTP_relay_agent">9.3.1. Configure dhcrelay as a DHCPv4 and BOOTP relay agent</a></span></dt><dt><span class="section"><a href="#sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent">9.3.2. Configure dhcrelay as a DHCPv6 relay agent</a></span></dt></dl></dd><dt><span class="sec
tion"><a href="#sec-Configuring_a_Multihomed_DHCP_Server">9.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-dns_Host_Configuration">9.4.1. Host Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-dhcp_for_ipv6_dhcpv6">9.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="#sec-dhcp-additional-resources">9.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-dhcp-installed-docs">9.6.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-DNS_Servers">10. DNS Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Introduction_to_DNS">10.1. Introduction to DNS</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-dns-introduction-zones">10.1.1. Nameserver Zones</a></span></dt><dt><span class="section"><a href="#sec-dns-introduction-nameservers">10.1.2. Nameserver Types</a>
</span></dt><dt><span class="section"><a href="#sec-dns-introduction-bind">10.1.3. BIND as a Nameserver</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-BIND">10.2. BIND</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-bind-empty-zones">10.2.1. Empty Zones</a></span></dt><dt><span class="section"><a href="#sec-bind-namedconf">10.2.2. Configuring the named Service</a></span></dt><dt><span class="section"><a href="#sec-bind-zone">10.2.3. Editing Zone Files</a></span></dt><dt><span class="section"><a href="#sec-bind-rndc">10.2.4. Using the rndc Utility</a></span></dt><dt><span class="section"><a href="#sec-bind-dig">10.2.5. Using the dig Utility</a></span></dt><dt><span class="section"><a href="#sec-bind-features">10.2.6. Advanced Features of BIND</a></span></dt><dt><span class="section"><a href="#sec-bind-mistakes">10.2.7. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="#sec-bind-additional-resources">10.2.8. Additional
Resources</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="appendix"><a href="#app-Revision_History">A. Revision History</a></span></dt><dt><span class="index"><a href="#idm225489704480">Index</a></span></dt></dl></div><div xml:lang="en-US" class="preface" id="idm225414215520" lang="en-US"><div class="titlepage"><div><div><h1 id="idm225414215520" class="title">Preface</h1></div></div></div><div class="para">
+ The <em class="citetitle">Networking Guide</em> contains information on how to use the networking related features of Fedora 20.
+ </div><div class="para">
+ This manual discusses many intermediate topics such as the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Setting up a network (from establishing an Ethernet connection using <span class="application"><strong>NetworkManager</strong></span> to configuring channel bonding interfaces).
+ </div></li><li class="listitem"><div class="para">
+ Configuring <code class="systemitem">DHCP</code>, <span class="application"><strong>BIND</strong></span>, and <code class="systemitem">DNS</code>.
+ </div></li></ul></div><div class="section" id="sec-Preface-Target_Audience"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1. Target Audience</h2></div></div></div><div class="para">
+ The <em class="citetitle">Networking Guide</em> assumes you have a basic understanding of the Fedora operating system. If you need help with the installation of this system, see the <em class="citetitle">Fedora 20 Installation Guide</em>.
+ </div><div class="para">
+ This guide is not aimed exclusively at experienced Linux system administrators. The authors of this book have attempted to cater for a wider audience as more and more organizations and users become subscribers to Red Hat, Inc. At the same time we are aware of the need not to allow seemingly trivial information to get in the way of the tasks. Your feedback on how well we have met this goal is welcome.
+ </div></div><div class="section" id="sec-Preface-About_this_book"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2. About This Book</h2></div></div></div><div class="para">
+ The <em class="citetitle">Networking Guide</em> is based on the networking material in the <a href="https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/index.html"><em class="citetitle">Red Hat Enterprise Linux 6 Deployment Guide</em></a>. It also retains the information on <code class="systemitem">DHCP</code> and <code class="systemitem">DNS</code> servers from the <a class="xref" href="#part-Servers">Part II, “Servers”</a> section. Most of the non-networking related material from the <em class="citetitle">Red Hat Enterprise Linux 6 Deployment Guide</em> guide can now be found in the <em class="citetitle">Fedora 20 System Administrator's Guide</em> except for reference material, such as that found in the appendices of the Deployment Guide.
+ </div></div><div class="section" id="sec-Whats-New"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3. What's new in Fedora 20</h2></div></div></div><div class="para">
+ <em class="firstterm">Network Teaming</em> has been introduced as an alternative to bonding for link aggregation. It is designed to be easy to maintain, debug and extend. For the user it offers performance and flexibility improvements and should be evaluated for all new installations.
+ </div><div class="para">
+ A new command-line tool, <span class="application"><strong>nmcli</strong></span>, has been introduced to allow users and scripts to interact with <span class="application"><strong>NetworkManager</strong></span>. A simple curses-based user interface for <span class="application"><strong>NetworkManager</strong></span>, <code class="command">nmtui</code>, is also available.
+ </div><div class="para">
+ A number of improvements have been made to <span class="application"><strong>NetworkManager</strong></span> to make it more suitable for use in server applications. In particular, <span class="application"><strong>NetworkManager</strong></span> no longer watches for configuration file changes by default, such as those made by editors or deployment tools. It allows administrators to make it aware of external changes through the <code class="command">nmcli connection reload</code> command. Changes made through <span class="application"><strong>NetworkManager</strong></span>'s D-Bus API or with <span class="application"><strong>nmcli</strong></span> are still effective immediately.
+ </div><div class="para">
+ Not included in this guide, but of interest to network administrators, is the new <em class="firstterm">Open Linux Management Infrastructure</em> or <span class="application"><strong>OpenLMI</strong></span> project. This is an implementation of open industry standards for remote system management, which includes an agent for networking. See the <em class="citetitle">Fedora 20 System Administrator's Guide</em> for information on the OpenLMI Networking Provider.
+ </div></div><div class="section" id="sec-Preface-Book_Organization"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4. How to Read this Book</h2></div></div></div><div class="para">
+ This manual is divided into the following main categories:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a class="xref" href="#part-Networking">Part I, “Networking”</a> </span></dt><dd><div class="para">
+ This part describes how to configure the network on Fedora.
+ </div><div class="para">
+ <a class="xref" href="#ch-Introduction_to_Fedora_Networking">Chapter 1, <em>Introduction to Fedora Networking</em></a> explains the default networking service, <span class="application"><strong>NetworkManager</strong></span>, and the various graphical and command-line tools that can be used to interact with <span class="application"><strong>NetworkManager</strong></span>. These include, an associated command-line configuration tool, <span class="application"><strong>nmcli</strong></span>, and two graphical user interface tools, <span class="application"><strong>control-center</strong></span> and <span class="application"><strong>nm-connection-editor</strong></span>. Read this chapter to learn more about the many ways the <span class="application"><strong>NetworkManager</strong></span> daemon can be used.
+ </div><div class="para">
+ <a class="xref" href="#ch-Configure_Networking">Chapter 2, <em>Configure Networking</em></a> covers static and dynamic interface settings, selecting network configuration methods, using <span class="application"><strong>NetworkManager</strong></span> with graphical and command-line user interfaces. Read this chapter to learn about configuring network connections.
+ </div><div class="para">
+ <a class="xref" href="#ch-Configure_Host_Names">Chapter 3, <em>Configure Host Names</em></a> covers static, pretty, and transient host names and their configuration using <span class="application"><strong>hostnamectl</strong></span>. Read this chapter to learn more about configuring host names on local and remote systems.
+ </div><div class="para">
+ <a class="xref" href="#ch-Configure_Network_Bonding">Chapter 4, <em>Configure Network Bonding</em></a> covers the configuring and use of bonded network connections. Read this chapter to learn about the configuring of network bonds using graphical and command-line user interfaces.
+ </div><div class="para">
+ <a class="xref" href="#ch-Configure_Network_Teaming">Chapter 5, <em>Configure Network Teaming</em></a> covers the configuring and use of teamed network connections. Read this chapter to learn about the configuring of network teams using graphical and command-line user interfaces.
+ </div><div class="para">
+ <a class="xref" href="#ch-Configure_Network_Bridging">Chapter 6, <em>Configure Network Bridging</em></a> covers the configuring and use of network bridges. Read this chapter to learn about the configuring of network bridges using graphical and command-line user interfaces.
+ </div><div class="para">
+ <a class="xref" href="#ch-Configure_802_1Q_VLAN_Tagging">Chapter 7, <em>Configure 802.1Q VLAN tagging</em></a> covers the configuring and use of virtual private networks, VLANs, according to the 802.1Q standard. Read this chapter to learn about the configuring of VLANs using graphical and command-line user interfaces.
+ </div><div class="para">
+ <a class="xref" href="#ch-Consistent_Network_Device_Naming">Chapter 8, <em>Consistent Network Device Naming</em></a> covers consistent network device naming for network interfaces, a feature that changes the name of network interfaces on a system in order to make locating and differentiating the interfaces easier. Read this chapter to learn about this feature and how to enable or disable it.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="#part-Servers">Part II, “Servers”</a></span></dt><dd><div class="para">
+ This part discusses how to set up servers normally required for networking.
+ </div><div class="para">
+ <a class="xref" href="#ch-DHCP_Servers">Chapter 9, <em>DHCP Servers</em></a> covers the installation of a Dynamic Host Configuration Protocol (<code class="systemitem">DHCP</code>) server and client. Read this chapter if you need to configure <code class="systemitem">DHCP</code> on your system.
+ </div><div class="para">
+ <a class="xref" href="#ch-DNS_Servers">Chapter 10, <em>DNS Servers</em></a> covers the Domain Name System (<code class="systemitem">DNS</code>), explains how to install, configure, run, and administer the <span class="application"><strong>BIND</strong></span> <code class="systemitem">DNS</code> server. Read this chapter if you need to configure a <code class="systemitem">DNS</code> server on your system.
+ </div></dd></dl></div><div class="para">
+ For topics related to network configuration but not listed above, such as configuring GRUB to enable serial links and the use of virtual console terminals, see the <em class="citetitle">Fedora 20 System Administrator's Guide</em>.
+ </div><div class="para">
+ For topics related to servers but not listed above, such as configuring Network Time Protocol (<code class="systemitem">NTP</code>) and Precision Time Protocol (<code class="systemitem">PTP</code>), see the <em class="citetitle">Fedora 20 System Administrator's Guide</em>.
+ </div></div><div xml:lang="en-US" class="section" id="idm225432817136" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm225432817136">5. Document Conventions</h2></div></div></div><div class="para">
+ This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
+ </div><div class="para">
+ In PDF and paper editions, this manual uses typefaces drawn from the <a href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a> set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.
+ </div><div class="section" id="idm225430776128"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225430776128">5.1. Typographic Conventions</h3></div></div></div><div class="para">
+ Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
+ </div><div class="para">
+ <code class="literal">Mono-spaced Bold</code>
+ </div><div class="para">
+ Used to highlight system input, including shell commands, file names and paths. Also used to highlight keycaps and key combinations. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ To see the contents of the file <code class="filename">my_next_bestselling_novel</code> in your current working directory, enter the <code class="command">cat my_next_bestselling_novel</code> command at the shell prompt and press <span class="keycap"><strong>Enter</strong></span> to execute the command.
+ </div></blockquote></div><div class="para">
+ The above includes a file name, a shell command and a keycap, all presented in mono-spaced bold and all distinguishable thanks to context.
+ </div><div class="para">
+ Key combinations can be distinguished from keycaps by the hyphen connecting each part of a key combination. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to execute the command.
+ </div><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> to switch to the first virtual terminal. Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F1</strong></span> to return to your X-Windows session.
+ </div></blockquote></div><div class="para">
+ The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with each set pressed simultaneously).
+ </div><div class="para">
+ If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in <code class="literal">mono-spaced bold</code>. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ File-related classes include <code class="classname">filesystem</code> for file systems, <code class="classname">file</code> for files, and <code class="classname">dir</code> for directories. Each class has its own associated set of permissions.
+ </div></blockquote></div><div class="para">
+ <span class="application"><strong>Proportional Bold</strong></span>
+ </div><div class="para">
+ This denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ Choose <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Mouse</strong></span> from the main menu bar to launch <span class="application"><strong>Mouse Preferences</strong></span>. In the <span class="guilabel"><strong>Buttons</strong></span> tab, click the <span class="guilabel"><strong>Left-handed mouse</strong></span> check box and click <span class="guibutton"><strong>Close</strong></span> to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).
+ </div><div class="para">
+ To insert a special character into a <span class="application"><strong>gedit</strong></span> file, choose <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>Accessories</strong></span> → <span class="guimenuitem"><strong>Character Map</strong></span> from the main menu bar. Next, choose <span class="guimenu"><strong>Search</strong></span> → <span class="guimenuitem"><strong>Find…</strong></span> from the <span class="application"><strong>Character Map</strong></span> menu bar, type the name of the character in the <span class="guilabel"><strong>Search</strong></span> field and click <span class="guibutton"><strong>Next</strong></span>. The character you sought will be highlighted in the <span class="guilabel"><strong>Character Table</strong></span>. Double-click this highlighted character to place it in the <span class="guilabel"><strong>Text to copy</strong></span> field and then click the <span class="guibutton"><stron
g>Copy</strong></span> button. Now switch back to your document and choose <span class="guimenu"><strong>Edit</strong></span> → <span class="guimenuitem"><strong>Paste</strong></span> from the <span class="application"><strong>gedit</strong></span> menu bar.
+ </div></blockquote></div><div class="para">
+ The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context.
+ </div><div class="para">
+ <code class="command"><em class="replaceable"><code>Mono-spaced Bold Italic</code></em></code> or <span class="application"><strong><em class="replaceable"><code>Proportional Bold Italic</code></em></strong></span>
+ </div><div class="para">
+ Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ To connect to a remote machine using ssh, type <code class="command">ssh <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>domain.name</code></em></code> at a shell prompt. If the remote machine is <code class="filename">example.com</code> and your username on that machine is john, type <code class="command">ssh john at example.com</code>.
+ </div><div class="para">
+ The <code class="command">mount -o remount <em class="replaceable"><code>file-system</code></em></code> command remounts the named file system. For example, to remount the <code class="filename">/home</code> file system, the command is <code class="command">mount -o remount /home</code>.
+ </div><div class="para">
+ To see the version of a currently installed package, use the <code class="command">rpm -q <em class="replaceable"><code>package</code></em></code> command. It will return a result as follows: <code class="command"><em class="replaceable"><code>package-version-release</code></em></code>.
+ </div></blockquote></div><div class="para">
+ Note the words in bold italics above — username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
+ </div><div class="para">
+ Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ Publican is a <em class="firstterm">DocBook</em> publishing system.
+ </div></blockquote></div></div><div class="section" id="idm225446127760"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225446127760">5.2. Pull-quote Conventions</h3></div></div></div><div class="para">
+ Terminal output and source code listings are set off visually from the surrounding text.
+ </div><div class="para">
+ Output sent to a terminal is set in <code class="computeroutput">mono-spaced roman</code> and presented thus:
+ </div><pre class="screen">books Desktop documentation drafts mss photos stuff svn
+books_tests Desktop1 downloads images notes scripts svgs</pre><div class="para">
+ Source-code listings are also set in <code class="computeroutput">mono-spaced roman</code> but add syntax highlighting as follows:
+ </div><pre class="programlisting">package org.<span class="perl_Function">jboss</span>.<span class="perl_Function">book</span>.<span class="perl_Function">jca</span>.<span class="perl_Function">ex1</span>;
+
+<span class="perl_Keyword">import</span> javax.naming.InitialContext;
+
+<span class="perl_Keyword">public</span> <span class="perl_Keyword">class</span> ExClient
+{
+ <span class="perl_Keyword">public</span> <span class="perl_DataType">static</span> <span class="perl_DataType">void</span> <span class="perl_Function">main</span>(String args[])
+ <span class="perl_Keyword">throws</span> Exception
+ {
+ InitialContext iniCtx = <span class="perl_Keyword">new</span> InitialContext();
+ Object ref = iniCtx.<span class="perl_Function">lookup</span>(<span class="perl_String">"EchoBean"</span>);
+ EchoHome home = (EchoHome) ref;
+ Echo echo = home.<span class="perl_Function">create</span>();
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Created Echo"</span>);
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Echo.echo('Hello') = "</span> + echo.<span class="perl_Function">echo</span>(<span class="perl_String">"Hello"</span>));
+ }
+}</pre></div><div class="section" id="idm225463597984"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225463597984">5.3. Notes and Warnings</h3></div></div></div><div class="para">
+ Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' will not cause data loss but may cause irritation and frustration.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
+ </div></div></div></div></div><div xml:lang="en-US" class="section" id="sec-Preface-Feedback" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6. Feedback</h2></div></div></div><a id="idm225443939920" class="indexterm"></a><div class="para">
+ If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in <a href="http://bugzilla.redhat.com/">Bugzilla</a> against the product <span class="application"><strong>Fedora Documentation</strong></span>.
+ </div><div class="para">
+ When submitting a bug report, be sure to provide the following information:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Manual's identifier: <code class="literal">networking-guide</code>
+ </div></li><li class="listitem"><div class="para">
+ Version number: <code class="literal">20</code>
+ </div></li></ul></div><div class="para">
+ If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
+ </div></div><div class="section" id="pref-Acknowledgments"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7. Acknowledgments</h2></div></div></div><div class="para">
+ Certain portions of this text first appeared in the <em class="citetitle">Red Hat Enterprise Linux 6 Deployment Guide</em>, copyright © 2014 Red Hat, Inc., available at <a href="https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/index.html">https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/index.html</a>.
+ </div></div></div><div class="part" id="part-Networking"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part I. Networking</h1></div></div></div><div class="partintro" id="idm225410233952"><div></div><div class="para">
+ This part describes how to configure the network on Fedora.
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#ch-Introduction_to_Fedora_Networking">1. Introduction to Fedora Networking</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-How_this_Book_is_Structured">1.1. How this Book is Structured</a></span></dt><dt><span class="section"><a href="#sec-Introduction_to_NetworkManager">1.2. Introduction to NetworkManager</a></span></dt><dt><span class="section"><a href="#sec-Installing_NetworkManager">1.3. Installing NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-The_NetworkManager_Daemon">1.3.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="#sec-Interacting_with_NetworkManager">1.3.2. Interacting with NetworkManager</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Network_Config_Using_CLI">1.4. Network Configuration Using the Command Line Interface (CLI)</a></span></dt><dt><span cl
ass="section"><a href="#sec-Network_Config_Using_nmcli">1.5. Network Configuration Using NetworkManager's CLI (nmcli)</a></span></dt><dt><span class="section"><a href="#sec-NetworkManager_and_the_Network_Scripts">1.6. NetworkManager and the Network Scripts</a></span></dt><dt><span class="section"><a href="#sec-Network_Configuration_Using_sysconfig_Files">1.7. Network Configuration Using sysconfig Files</a></span></dt><dt><span class="section"><a href="#sec-Introduction_to_Fedora_Networking-additional_resources">1.8. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Introduction_to_Fedora_Networking-docs-inst">1.8.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configure_Networking">2. Configure Networking</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Static_and_Dynamic_Interface_Settings">2.1. Static and Dynamic Interface Settings</a></span></dt><dd><dl><dt><span class="se
ction"><a href="#sec-When_to_Use_Static_Network_Interface_Settings">2.1.1. When to Use Static Network Interface Settings</a></span></dt><dt><span class="section"><a href="#sec-When_to_Use_Dynamic_Interface_Settings">2.1.2. When to Use Dynamic Interface Settings</a></span></dt><dt><span class="section"><a href="#sec-Selecting_Network_Configuration_Methods">2.1.3. Selecting Network Configuration Methods</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface">2.2. Using NetworkManager with the GNOME Graphical User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Connecting_to_a_Network_Using_a_GUI">2.2.1. Connecting to a Network Using a GUI</a></span></dt><dt><span class="section"><a href="#sec-Configuring_New_and_Editing_Existing_Connections">2.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="#sec-Connecting_to_a_Network_Automati
cally">2.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="#sec-System-wide_and_Private_Connection_Profiles">2.2.4. System-wide and Private Connection Profiles</a></span></dt><dt><span class="section"><a href="#sec-Configuring_a_Wired_Ethernet_Connection">2.2.5. Configuring a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="#sec-Configuring_a_Wi-Fi_Connection">2.2.6. Configuring a Wi-Fi Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_VPN_Connection">2.2.7. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_Mobile_Broadband_Connection">2.2.8. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_DSL_Connection">2.2.9. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Connection_Settings">2.2.10. Configuring Connection Se
ttings</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_the_Command_Line_Interface">2.3. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configuring_a_Network_Interface_Using_ifcg_Files">2.3.1. Configuring a Network Interface Using ifcfg Files</a></span></dt><dt><span class="section"><a href="#sec-Configuring_a_Network_Interface_Using_ip_commands">2.3.2. Configuring a Network Interface Using ip Commands</a></span></dt><dt><span class="section"><a href="#sec-Static-Routes_and_the_Default_Gateway">2.3.3. Static Routes and the Default Gateway</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Static_Routes_in_ifcfg_files">2.3.4. Configuring Static Routes in ifcfg files</a></span></dt><dt><span class="section"><a href="#sec-Configuring_IPv6_Tokenized_Interface_Identifiers">2.3.5. Configuring IPv6 Tokenized Interface Identifiers</a></span></dt></dl></dd><dt><span class="section"><a href="#
sec-Using_the_NetworkManager_Command_Line_Tool_nmcli">2.4. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Understanding_the_nmcli_Options">2.4.1. Understanding the nmcli Options</a></span></dt><dt><span class="section"><a href="#sec-Connecting_to_a_Network_Using_nmcli">2.4.2. Connecting to a Network Using nmcli</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Static_Routes_Using_nmcli">2.4.3. Configuring Static Routes Using nmcli</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_Networking-additional_resources">2.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configure_Networking-docs-inst">2.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-Configure_Networking_Online_Documentation">2.5.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configure_H
ost_Names">3. Configure Host Names</a></span></dt><dd><dl><dt><span class="section"><a href="#sec_Understanding_Host_Names">3.1. Understanding Host Names</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Recommended_Naming_Practices">3.1.1. Recommended Naming Practices</a></span></dt></dl></dd><dt><span class="section"><a href="#sec_Configuring_Host_Names_Using_hostnamectl">3.2. Configuring Host Names Using hostnamectl</a></span></dt><dd><dl><dt><span class="section"><a href="#sec_View_All_the_Host_Names">3.2.1. View All the Host Names</a></span></dt><dt><span class="section"><a href="#sec_Set_All_the_Host_Names">3.2.2. Set All the Host Names</a></span></dt><dt><span class="section"><a href="#sec_Set_a_Particular_Host_Name">3.2.3. Set a Particular Host Name</a></span></dt><dt><span class="section"><a href="#sec_Clear_a_Particular_Host_Name">3.2.4. Clear a Particular Host Name</a></span></dt><dt><span class="section"><a href="#sec_Changing_Host_Names_Remotely">3.
2.5. Changing Host Names Remotely</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Host_Names_Using_nmcli">3.3. Configuring Host Names Using nmcli</a></span></dt><dt><span class="section"><a href="#sec-additional_resources">3.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-hostnamectl-docs-inst">3.4.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-hostnamectl-Online_Documentation">3.4.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configure_Network_Bonding">4. Configure Network Bonding</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Bond-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces">4.1. Understanding the Default Behavior of Master and Slave Interfaces</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Bond_Connection_Using_a_GUI">4.2. Creating a Bond Connection Using a GUI</a
></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_Bond_Connection">4.2.1. Establishing a Bond Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Network_Bonding_Using_the_Command_Line_Interface">4.3. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Check_if_Bonding_Kernel_Module_is_Installed">4.3.1. Check if Bonding Kernel Module is Installed</a></span></dt><dt><span class="section"><a href="#sec-Create_a_Channel_Bonding_Interface">4.3.2. Create a Channel Bonding Interface</a></span></dt><dt><span class="section"><a href="#sec-Creating_SLAVE_Interfaces">4.3.3. Creating SLAVE Interfaces</a></span></dt><dt><span class="section"><a href="#sec-Activating_a_Channel_Bond">4.3.4. Activating a Channel Bond</a></span></dt><dt><span class="section"><a href="#sec-Creating_Multiple_Bonds">4.3.5. Creating Multiple Bonds</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-U
sing_Channel_Bonding">4.4. Using Channel Bonding</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-modules-bonding-directives">4.4.1. Bonding Module Directives</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli">4.5. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="#sec-Configure_Network_Bonding-additional_resources">4.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configure_Network_Bonding-docs-inst">4.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-Configure_Network_Bonding_Online_Documentation">4.6.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configure_Network_Teaming">5. Configure Network Teaming</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Understanding_Network_Teaming">5.1. Understandi
ng Network Teaming</a></span></dt><dt><span class="section"><a href="#sec-Comparison_of_Network_Teaming_to_Bonding">5.2. Comparison of Network Teaming to Bonding</a></span></dt><dt><span class="section"><a href="#sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces">5.3. Understanding the Default Behavior of Master and Slave Interfaces</a></span></dt><dt><span class="section"><a href="#sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners">5.4. Understanding the Network Teaming Daemon and the "Runners"</a></span></dt><dt><span class="section"><a href="#sec-Install_the_Network_Teaming_Daemon">5.5. Install the Network Teaming Daemon</a></span></dt><dt><span class="section"><a href="#sec-Converting_a_Bond_to_a_Team">5.6. Converting a Bond to a Team</a></span></dt><dt><span class="section"><a href="#sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team">5.7. Selecting Interfaces to Use as Ports for a Network Team</a></span></dt><dt><span class="
section"><a href="#sec-Selecting_Network_Team_Configuration_Methods">5.8. Selecting Network Team Configuration Methods</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Network_Team_Using_a_GUI">5.9. Creating a Network Team Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_Team_Connection">5.9.1. Establishing a Team Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_a_Network_Team_Using-the_Command_Line">5.10. Configure a Network Team Using the Command Line</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Creating_a_Network_Team_Using_teamd">5.10.1. Creating a Network Team Using teamd</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Network_Team_Using_ifcfg_Files">5.10.2. Creating a Network Team Using ifcfg Files</a></span></dt><dt><span class="section"><a href="#sec-Add_a_port_to_a_Network_Team_Using_iputils">5.10.3. Add a Port to a Network Team Using ip
utils</a></span></dt><dt><span class="section"><a href="#sec-Listing_the_ports_of_a_Team_Using_teamnl">5.10.4. Listing the ports of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Options_of_a_Team_Using_teamnl">5.10.5. Configuring Options of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="#sec-Add_an_address_to_a_Network_Team_Using_iputils">5.10.6. Add an Address to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="#sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils">5.10.7. Bring up an Interface to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="#sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl">5.10.8. Viewing the Active Port Options of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="#sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl">5.10.9. Setting the Active Port Options of a Team Using teamnl</a></span></dt></dl></d
d><dt><span class="section"><a href="#sec-Controlling_teamd_with_teamdctl">5.11. Controlling teamd with teamdctl</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Add_a_port_to_a_Network_Team">5.11.1. Add a Port to a Network Team</a></span></dt><dt><span class="section"><a href="#sec-Remove_a_Port_From_a_Network_Team">5.11.2. Remove a Port From a Network Team</a></span></dt><dt><span class="section"><a href="#sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team">5.11.3. Apply a Configuration to a Port in a Network Team</a></span></dt><dt><span class="section"><a href="#sec-View_the_Configuration_of_a_Port_in_a_Network_Team">5.11.4. View the Configuration of a Port in a Network Team</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_teamd_Runners">5.12. Configure teamd Runners</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configure_the_broadcast_Runner">5.12.1. Configure the broadcast Runner</a></span></dt><dt><span class
="section"><a href="#sec-Configure_the_random_Runner">5.12.2. Configure the random Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_the_roundrobin_Runner">5.12.3. Configure the roundrobin Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_the_activebackup_Runner">5.12.4. Configure the activebackup Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_the_loadbalance_Runner">5.12.5. Configure the loadbalance Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_the_LACP_Runner">5.12.6. Configure the LACP (802.3ad) Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_Monitoring_of_the_Link_State">5.12.7. Configure Monitoring of the Link State</a></span></dt><dt><span class="section"><a href="#sec-Configure_Port_Selection_Override">5.12.8. Configure Port Selection Override</a></span></dt><dt><span class="section"><a href="#sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computa
tion_Algorithm">5.12.9. Configure BPF-based Tx Port Selectors</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_Network_Teaming_Using_nmcli">5.13. Configure Network Teaming Using nmcli</a></span></dt><dt><span class="section"><a href="#sec-Network_Teaming-additional_resources">5.14. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-teamd-docs-inst">5.14.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-teamd_docs-online">5.14.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configure_Network_Bridging">6. Configure Network Bridging</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configure_Network_Bridging_Using_a_GUI">6.1. Configure Network Bridging Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_Bridge_Connection">6.1.1. Establishing a Bridge Connection</a></span></dt></dl></dd><dt
><span class="section"><a href="#sec-Network_Bridging_Using_the_Command_Line_Interface">6.2. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Check_if_Bridging_Kernel_Module_is_Installed">6.2.1. Check if Bridging Kernel Module is Installed</a></span></dt><dt><span class="section"><a href="#sec-Create_a_Network_Bridge">6.2.2. Create a Network Bridge</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli">6.3. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="#sec-Network_Bridging-additional_resources">6.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Network_Bridging-docs-inst">6.4.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configure_802_1Q_VLAN_Tagging">7. Configure 802.1Q VLAN tagging</a></span></dt
><dd><dl><dt><span class="section"><a href="#sec-Selecting_VLAN_Interface_Configuration_Methods">7.1. Selecting VLAN Interface Configuration Methods</a></span></dt><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI">7.2. Configure 802.1Q VLAN Tagging Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_VLAN_Connection">7.2.1. Establishing a VLAN Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line">7.3. Configure 802.1Q VLAN Tagging Using the Command Line</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_Up_802.1Q_VLAN_Tagging_Using_ifcfg_Files">7.3.1. Setting Up 802.1Q VLAN Tagging Using ifcfg Files</a></span></dt><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging_ip_Commands">7.3.2. Configure 802.1Q VLAN Tagging Using ip Commands</a></span></dt></dl></dd><dt><span class="section"><a href="#se
c-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli">7.4. Configure 802.1Q VLAN Tagging Using the Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging-additional_resources">7.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging-docs-inst">7.5.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Consistent_Network_Device_Naming">8. Consistent Network Device Naming</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Naming_Schemes_Hierarchy">8.1. Naming Schemes Hierarchy</a></span></dt><dt><span class="section"><a href="#sec-Understanding_the_Device_Renaming_Procedure">8.2. Understanding the Device Renaming Procedure</a></span></dt><dt><span class="section"><a href="#sec-Understanding_the_Predictable_Network_Interface_Device_Names">8.3. Understanding the Predictable Network Interface De
vice Names</a></span></dt><dt><span class="section"><a href="#sec-Naming_Scheme_for_Network_Devices_Available_for_Linux_on_System_z">8.4. Naming Scheme for Network Devices Available for Linux on System z</a></span></dt><dt><span class="section"><a href="#sec-Naming_Scheme_for_VLAN_Interfaces">8.5. Naming Scheme for VLAN Interfaces</a></span></dt><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming_Using_biosdevname">8.6. Consistent Network Device Naming Using biosdevname</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming-System_Requirements">8.6.1. System Requirements</a></span></dt><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming-Enabling_and_Disabling">8.6.2. Enabling and Disabling the Feature</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming-Notes">8.7. Notes for Administrators</a></span></dt><dt><span class="section"><a href="#sec-Contr
olling_the_Selection_of_Network_Device_Names">8.8. Controlling the Selection of Network Device Names</a></span></dt><dt><span class="section"><a href="#sec-Disabling_Consistent_Network_Device_Naming">8.9. Disabling Consistent Network Device Naming</a></span></dt><dt><span class="section"><a href="#sec_Troubleshooting_Network_Device_Naming">8.10. Troubleshooting Network Device Naming</a></span></dt><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming-additional_resources">8.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming-docs-inst">8.11.1. Installed Documentation</a></span></dt></dl></dd></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" id="ch-Introduction_to_Fedora_Networking" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 1. Introduction to Fedora Networking</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a
href="#sec-How_this_Book_is_Structured">1.1. How this Book is Structured</a></span></dt><dt><span class="section"><a href="#sec-Introduction_to_NetworkManager">1.2. Introduction to NetworkManager</a></span></dt><dt><span class="section"><a href="#sec-Installing_NetworkManager">1.3. Installing NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-The_NetworkManager_Daemon">1.3.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="#sec-Interacting_with_NetworkManager">1.3.2. Interacting with NetworkManager</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Network_Config_Using_CLI">1.4. Network Configuration Using the Command Line Interface (CLI)</a></span></dt><dt><span class="section"><a href="#sec-Network_Config_Using_nmcli">1.5. Network Configuration Using NetworkManager's CLI (nmcli)</a></span></dt><dt><span class="section"><a href="#sec-NetworkManager_and_the_Network_Scripts">1.6. NetworkManager and the Netwo
rk Scripts</a></span></dt><dt><span class="section"><a href="#sec-Network_Configuration_Using_sysconfig_Files">1.7. Network Configuration Using sysconfig Files</a></span></dt><dt><span class="section"><a href="#sec-Introduction_to_Fedora_Networking-additional_resources">1.8. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Introduction_to_Fedora_Networking-docs-inst">1.8.1. Installed Documentation</a></span></dt></dl></dd></dl></div><div class="section" id="sec-How_this_Book_is_Structured"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.1. How this Book is Structured</h2></div></div></div><div class="para">
+ All new material in this book has been written and arranged in such a way as to clearly separate introductory material, such as explanations of concepts and use cases, from configuration tasks. The authors hope that you can quickly find configuration instructions you need, while still providing some relevant explanations and conceptual material to help you understand and decide on the appropriate tasks relevant to your needs. Where material has been reused from the <a href="https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/index.html"><em class="citetitle">Red Hat Enterprise Linux 6 Deployment Guide</em></a>, it has been reviewed and changed, where possible, to fit this idea of separating concepts from tasks.
+ </div><div class="para">
+ The material is grouped according to the goal rather than the method. Instructions on how to achieve a specific task using different methods are grouped together. This is intended to make it easier for you to find the information on how to achieve a particular task or goal, and at the same time allow you to quickly see the different methods available.
+ </div><div class="para">
+ In each chapter, the configuration methods will be presented in the following order: A graphical user interface (GUI) method, such as the use of <span class="application"><strong>nm-connection-editor</strong></span> or <span class="application"><strong>control-network</strong></span> to direct <code class="systemitem">NetworkManager</code>, then <span class="application"><strong>NetworkManager</strong></span>'s command-line tool <span class="application"><strong>nmcli</strong></span>, and then finally methods using the command line and configuration files. The command line can be used to issue commands and to compose or edit configuration files, therefore the use of the <span class="application"><strong>ip</strong></span> commands and configuration files will be documented together.
+ </div></div><div class="section" id="sec-Introduction_to_NetworkManager"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.2. Introduction to NetworkManager</h2></div></div></div><div class="para">
+ As of Fedora 20, the default networking service is provided by <code class="systemitem">NetworkManager</code>, which is a dynamic network control and configuration daemon that attempts to keep network devices and connections up and active when they are available. The traditional <code class="filename">ifcfg</code> type configuration files are still supported. See <a class="xref" href="#sec-NetworkManager_and_the_Network_Scripts">Section 1.6, “NetworkManager and the Network Scripts”</a> for more information.
+ </div><div class="table" id="tb-A_Summary_of_Networking_Tools_and_Applications"><h6>Table 1.1. A Summary of Networking Tools and Applications</h6><div class="table-contents"><table summary="A Summary of Networking Tools and Applications" border="1"><colgroup><col width="29%" align="left" class="c1" /><col width="71%" align="left" class="c2" /></colgroup><thead><tr><th class="" align="left">
+ Application or Tool
+ </th><th class="" align="left">
+ Description
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ <span class="application"><strong>NetworkManager</strong></span>
+ </td><td class="" align="left">
+ The default networking daemon
+ </td></tr><tr><td class="" align="left">
+ <span class="application"><strong>nmtui</strong></span>
+ </td><td class="" align="left">
+ A simple curses-based text user interface (TUI) for <span class="application"><strong>NetworkManager</strong></span>
+ </td></tr><tr><td class="" align="left">
+ <span class="application"><strong>nmcli</strong></span>
+ </td><td class="" align="left">
+ A command-line tool provided to allow users and scripts to interact with <span class="application"><strong>NetworkManager</strong></span>
+ </td></tr><tr><td class="" align="left">
+ <span class="application"><strong>control-center</strong></span>
+ </td><td class="" align="left">
+ A graphical user interface tool provided by the GNOME Shell
+ </td></tr><tr><td class="" align="left">
+ <span class="application"><strong>nm-connection-editor</strong></span>
+ </td><td class="" align="left">
+ A GTK+ 3 application available for certain tasks not yet handled by <span class="application"><strong>control-center</strong></span>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ <code class="systemitem">NetworkManager</code> can be used with the following types of connections: Ethernet, VLANs, Bridges, Bonds, Teams, Wi-Fi, mobile broadband (such as cellular 3G), and IP-over-InfiniBand. For these connection types, <code class="systemitem">NetworkManager</code> can configure network aliases, <code class="systemitem">IP</code> addresses, static routes, <code class="systemitem">DNS</code> information, and VPN connections, as well as many connection-specific parameters. Finally, <code class="systemitem">NetworkManager</code> provides an API via D-Bus which allows applications to query and control network configuration and state.
+ </div></div><div class="section" id="sec-Installing_NetworkManager"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.3. Installing NetworkManager</h2></div></div></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> is installed by default on Fedora. If necessary, to ensure that it is, run the following command as the <code class="systemitem">root</code> user:
+ </div><pre class="screen">~]# <code class="command">yum install NetworkManager</code></pre><div class="para">
+ For information on user privileges and gaining privileges, see the <em class="citetitle">Fedora 20 System Administrator's Guide</em>.
+ </div><div class="section" id="sec-The_NetworkManager_Daemon"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.3.1. The NetworkManager Daemon</h3></div></div></div><div class="para">
+ The <span class="application"><strong>NetworkManager</strong></span> daemon runs with root privileges and is, by default, configured to start up at boot time. You can determine whether the <span class="application"><strong>NetworkManager</strong></span> daemon is running by entering this command:
+ </div><pre class="screen">~]$ <code class="command">systemctl status NetworkManager</code>
+NetworkManager.service - Network Manager
+ Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled)
+ Active: active (running) since Fri, 08 Mar 2013 12:50:04 +0100; 3 days ago</pre><div class="para">
+ The <code class="command">systemctl status</code> command will report <span class="application"><strong>NetworkManager</strong></span> as <code class="computeroutput">Active: inactive (dead)</code> if the <span class="application"><strong>NetworkManager</strong></span> service is not running. To start it for the current session run the following command as the root user:
+ </div><pre class="screen">~]# <code class="command">systemctl start NetworkManager</code></pre><div class="para">
+ Run the <code class="command">systemctl enable</code> command to ensure that <span class="application"><strong>NetworkManager</strong></span> starts up every time the system boots:
+ </div><pre class="screen">~]# <code class="command">systemctl enable NetworkManager</code></pre><div class="para">
+ For more information on starting, stopping and managing services, see the <em class="citetitle">Fedora 20 System Administrator's Guide</em>.
+ </div></div><div class="section" id="sec-Interacting_with_NetworkManager"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.3.2. Interacting with NetworkManager</h3></div></div></div><div class="para">
+ Users do not interact with the <span class="application"><strong>NetworkManager</strong></span> system service directly. Instead, users perform network configuration tasks via graphical and command-line user interface tools. The following tools are available in Fedora:
+ </div><div class="para">
+ <div class="orderedlist"><ol><li class="listitem"><div class="para">
+ A graphical user interface tool called <span class="application"><strong>control-center</strong></span>, provided by GNOME, is available for desktop users. It incorporates a <span class="application"><strong>Network</strong></span> settings tool. It start it, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ A command-line tool, <span class="application"><strong>nmcli</strong></span>, is provided to allow users and scripts to interact with <span class="application"><strong>NetworkManager</strong></span>. Note that <span class="application"><strong>nmcli</strong></span> can be used on GUI-less systems like servers to control all aspects of <span class="application"><strong>NetworkManager</strong></span>. It is on an equal footing with the GUI tools.
+ </div></li><li class="listitem"><div class="para">
+ The GNOME Shell also provides a network icon in its Notification Area representing network connection states as reported by <span class="application"><strong>NetworkManager</strong></span>. The icon has multiple states that serve as visual indicators for the type of connection you are currently using.
+ </div></li><li class="listitem"><div class="para">
+ A graphical user interface tool called <span class="application"><strong>control-center</strong></span>, provided by the GNOME Shell, is available for desktop users. It incorporates a <span class="application"><strong>Network</strong></span> settings tool. To start it, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="keycap"><strong>Super</strong></span> key appears in a variety of guises, depending on the keyboard and other hardware, but often as either the Windows or Command key, and typically to the left of the Spacebar.
+ </div></li><li class="listitem"><div class="para">
+ A graphical user interface tool, <span class="application"><strong>nm-connection-editor</strong></span>, is available for certain tasks not yet handled by <span class="application"><strong>control-center</strong></span>. To start it, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">network connections</code> or <code class="command">nm-connection-editor</code> and then press <span class="keycap"><strong>Enter</strong></span>.
+ </div></li></ol></div>
+
+ </div></div></div><div class="section" id="sec-Network_Config_Using_CLI"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.4. Network Configuration Using the Command Line Interface (CLI)</h2></div></div></div><div class="para">
+ </div><div class="para">
+ The commands for the <span class="application"><strong>ip</strong></span> utility, sometimes referred to as <span class="package">iproute2</span> after the upstream package name, are documented in the <code class="filename">man ip(8)</code> page. The package name in Fedora is <span class="package">iproute</span>. If necessary, you can check that the <span class="application"><strong>ip</strong></span> utility is installed by checking its version number as follows:
+ </div><pre class="screen">~]$ <code class="command">ip -V</code>
+ip utility, iproute2-ss130716</pre><div class="para">
+ The <span class="application"><strong>ip</strong></span> commands can be used to add and remove addresses and routes to interfaces in parallel with <span class="application"><strong>NetworkManager</strong></span>, which will preserve them and recognize them in <span class="application"><strong>nmcli</strong></span>, <span class="application"><strong>nmtui</strong></span>, <span class="application"><strong>control-center</strong></span>, and the D-Bus API.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that <span class="application"><strong>ip</strong></span> commands given on the command line will not persist after a system restart.
+ </div></div></div><div class="para">
+ Examples of using the command line and configuration files for each task are included after explaining the use of one of the graphical user interfaces to <span class="application"><strong>NetworkManager</strong></span>, namely, <span class="application"><strong>control-center</strong></span> and <span class="application"><strong>nm-connection-editor</strong></span>.
+ </div></div><div class="section" id="sec-Network_Config_Using_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.5. Network Configuration Using NetworkManager's CLI (nmcli)</h2></div></div></div><div class="para">
+ </div><div class="para">
+ The <span class="application"><strong>NetworkManager</strong></span> command-line tool, <span class="application"><strong>nmcli</strong></span>, provides a command line way to configure networking by controlling <span class="application"><strong>NetworkManager</strong></span>. It is installed, along with <span class="application"><strong>NetworkManager</strong></span>, by default. If required, for details on how to verify that <span class="application"><strong>NetworkManager</strong></span> is running, see <a class="xref" href="#sec-The_NetworkManager_Daemon">Section 1.3.1, “The NetworkManager Daemon”</a>.
+ </div><div class="para">
+ Examples of using the <span class="application"><strong>nmcli</strong></span> tool for each task will be included where possible, after explaining the use of graphical user interfaces and other command line methods. See <a class="xref" href="#sec-Using_the_NetworkManager_Command_Line_Tool_nmcli">Section 2.4, “Using the NetworkManager Command Line Tool, nmcli”</a> for an introduction to <span class="application"><strong>nmcli</strong></span>.
+ </div></div><div class="section" id="sec-NetworkManager_and_the_Network_Scripts"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.6. NetworkManager and the Network Scripts</h2></div></div></div><div class="para">
+ In previous Red Hat Enterprise Linux releases, the default way to configure networking was using <em class="firstterm">network scripts</em>. The term <em class="firstterm">network scripts</em> is commonly used for the script <code class="filename">/etc/init.d/network</code> and any other installed scripts it calls. The user supplied files are typically viewed as configuration, but can also be interpreted as an amendment to the scripts.
+ </div><div class="para">
+ Although <span class="application"><strong>NetworkManager</strong></span> provides the default networking service, Red Hat developers have worked hard to ensure that scripts and <span class="application"><strong>NetworkManager</strong></span> cooperate with each other. Administrators who are used to the scripts can certainly continue to use them. We expect both systems to be able to run in parallel and work well together. It is expected that most user shell scripts from previous releases will still work. Red Hat recommends that you test them first.
+ </div><h3 id="bh-Running_Network_Script">Running Network Script</h3><div class="para">
+ Run the script <span class="bold bold"><strong>only</strong></span> with the <span class="application"><strong>systemctl</strong></span> utility which will clear any existing environment variables and ensure clean execution. The command takes the following form: <pre class="synopsis"><code class="command">systemctl <code class="option">start|stop|restart|status</code> network</code></pre>
+ </div><div class="para">
+ <span class="bold bold"><strong>Do not run</strong></span> any service by calling <code class="command">/etc/init.d/<em class="replaceable"><code>servicename</code></em> <code class="option">start|stop|restart|status</code></code> directly.
+ </div><div class="para">
+ Note that in Red Hat Enterprise Linux 7, <span class="application"><strong>NetworkManager</strong></span> is started first, and <code class="filename">/etc/init.d/network</code> checks with <span class="application"><strong>NetworkManager</strong></span> to avoid tampering with <span class="application"><strong>NetworkManager</strong></span>'s connections. <span class="application"><strong>NetworkManager</strong></span> is intended to be the primary application using sysconfig configuration files and <code class="filename">/etc/init.d/network</code> is intended to be secondary, playing a fallback role.
+ </div><div class="para">
+ The <code class="filename">/etc/init.d/network</code> script is not event-driven, it runs either:
+ <div class="orderedlist"><ol><li class="listitem"><div class="para">
+ manually (by one of the <code class="command">systemctl</code> commands <code class="command"><code class="option">start|stop|restart</code> network</code>),
+ </div></li><li class="listitem"><div class="para">
+ on boot and shutdown if the network service is enabled (as a result of the command <code class="command">systemctl enable network</code>).
+ </div></li></ol></div>
+ It is a manual process and does not react to events that happen after boot. Users can also call the scripts <code class="filename">ifup</code> and <code class="filename">ifdown</code> manually.
+ </div><div class="para">
+
+ </div><h3 id="bh-Custom_Commands_and_the_Network_Scripts">Custom Commands and the Network Scripts</h3><div class="para">
+ Custom commands in the scripts <code class="filename">/sbin/ifup-local</code>, <code class="filename">ifdown-pre-local</code>, and <code class="filename">ifdown-local</code> are only executed when those devices are controlled by the <code class="systemitem">/etc/init.d/network</code> service. If you modified the initscripts themselves (for example, <code class="filename">/etc/sysconfig/network-scripts/ifup-eth</code>) then those changes would be overwritten by an <span class="package">initscripts</span> package update. Therefore it is recommend that you avoid modifying the initscripts directly and make use of the <code class="filename">/sbin/if*local</code> scripts, so that your custom changes will survive package updates. The initscripts just check for the presence of the relevant <code class="filename">/sbin/if*local</code> and run them if they exit. The initscripts do not place anything in the <code class="filename">/sbin/if*local</code> scripts, nor does the <span cla
ss="package">initscripts</span> RPM (or any package) own or modify those files.
+ </div><div class="para">
+ There are ways to perform custom tasks when network connections go up and down, both with the old network scripts and with <span class="application"><strong>NetworkManager</strong></span>. When <span class="application"><strong>NetworkManager</strong></span> is enabled, the <code class="filename">ifup</code> and <code class="filename">ifdown</code> script will ask <span class="application"><strong>NetworkManager</strong></span> whether <span class="application"><strong>NetworkManager</strong></span> manages the interface in question, which is found from the <span class="quote">“<span class="quote">DEVICE=</span>”</span> line in the <code class="filename">ifcfg</code> file. If <span class="application"><strong>NetworkManager</strong></span> does manage that device, and the device is not already connected, then <code class="filename">ifup</code> will ask <span class="application"><strong>NetworkManager</strong></span> to start the connection.
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If the device is managed by <span class="application"><strong>NetworkManager</strong></span> and it <span class="bold bold"><strong>is</strong></span> already connected, nothing is done.
+ </div></li><li class="listitem"><div class="para">
+ If the device is not managed by <span class="application"><strong>NetworkManager</strong></span>, then the scripts will start the connection using the older, non-<span class="application"><strong>NetworkManager</strong></span> mechanisms that they have used since the time before <span class="application"><strong>NetworkManager</strong></span> existed.
+ </div></li></ul></div>
+ </div><div class="para">
+ If you are calling "<code class="filename">ifdown</code>" and the device is managed by <span class="application"><strong>NetworkManager</strong></span>, then <code class="filename">ifdown</code> will ask <span class="application"><strong>NetworkManager</strong></span> to terminate the connection.
+ </div><div class="para">
+ The scripts dynamically check <span class="application"><strong>NetworkManager</strong></span>, so if <span class="application"><strong>NetworkManager</strong></span> is not running, the scripts will fall back to the old, pre-<span class="application"><strong>NetworkManager</strong></span> script-based mechanisms.
+ </div></div><div class="section" id="sec-Network_Configuration_Using_sysconfig_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.7. Network Configuration Using sysconfig Files</h2></div></div></div><div class="para">
+ The <code class="filename">/etc/sysconfig/</code> directory is a location for configuration files and scripts. Most network configuration information is stored there, with the exception of VPN, mobile broadband and PPPoE configuration, which are stored in <code class="filename">/etc/NetworkManager/</code> subdirectories. Interface specific information for example, is stored in <code class="filename">ifcfg</code> files in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory.
+ </div><div class="para">
+ The file <code class="filename">/etc/sysconfig/network</code> is for global settings. Information for VPNs, mobile broadband and PPPoE connections is stored in <code class="filename">/etc/NetworkManager/system-connections/</code>.
+ </div><div class="para">
+ In Fedora, when you edit an <code class="filename">ifcfg</code> file, <span class="application"><strong>NetworkManager</strong></span> is not automatically aware of the change and has to be prompted to notice the change. If you use one of the tools to update <span class="application"><strong>NetworkManager</strong></span> profile settings, then <span class="application"><strong>NetworkManager</strong></span> does not implement those changes until you reconnect using that profile. For example, if configuration files have been changed using an editor, <span class="application"><strong>NetworkManager</strong></span> must be told to read the configuration files again. To do that, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">nmcli connection reload</code></pre>
+ The above command reads all connection profiles. Alternatively, to reload only one changed file, <code class="filename">ifcfg-<em class="replaceable"><code>ifname</code></em></code>, issue a command as follows:
+<pre class="screen">~]# <code class="command">nmcli con load /etc/sysconfig/network-scripts/ifcfg-<em class="replaceable"><code>ifname</code></em></code></pre>
+ The command accepts multiple file names. These commands require <code class="systemitem">root</code> privileges. For more information on user privileges and gaining privileges, see the <em class="citetitle">Fedora 20 System Administrator's Guide</em> and the <code class="filename">su(1)</code> and <code class="filename">sudo(8)</code> man pages.
+ </div><div class="para">
+ Changes made using tools such as <span class="application"><strong>nmcli</strong></span> do not require a reload but do require the associated interface to be put down and then up again. That can be done by using commands in the following format: <pre class="synopsis">nmcli dev disconnect <em class="replaceable"><code>interface-name</code></em></pre> Followed by: <pre class="synopsis">nmcli con up <em class="replaceable"><code>interface-name</code></em></pre>
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> does not trigger any of the network scripts, though the network scripts will try to trigger <span class="application"><strong>NetworkManager</strong></span> if it is running when <code class="filename">ifup</code> commands are used. See <a class="xref" href="#sec-NetworkManager_and_the_Network_Scripts">Section 1.6, “NetworkManager and the Network Scripts”</a> for an explanation of the network scripts.
+ </div><div class="para">
+ The <code class="filename">ifup</code> script is a generic script which does a few things and then calls interface-specific scripts like <code class="filename">ifup-ethX</code>, <code class="filename">ifup-wireless</code>, <code class="filename">ifup-ppp</code>, and so on. When a user runs <code class="command">ifup eth0</code> manually, the following occurs:
+ <div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <code class="filename">ifup</code> looks for a file called <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth0</code>;
+ </div></li><li class="listitem"><div class="para">
+ if the <code class="filename">ifcfg</code> file exists, <code class="filename">ifup</code> looks for the <code class="option">TYPE</code> key in that file to determine which type-specific script to call;
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ifup</code> calls <code class="filename">ifup-wireless</code> or <code class="filename">ifup-eth</code> or <code class="filename">ifup-XXX</code> based on <code class="option">TYPE</code>;
+ </div></li><li class="listitem"><div class="para">
+ the type-specific scripts do type-specific setup;
+ </div></li><li class="listitem"><div class="para">
+ and then the type-specific scripts let common functions perform <code class="systemitem">IP</code>-related tasks like <code class="systemitem">DHCP</code> or static setup.
+ </div></li></ol></div>
+
+ </div><div class="para">
+ On bootup, <code class="filename">/etc/init.d/network</code> reads through all the <code class="filename">ifcfg</code> files and for each one that has <code class="command">ONBOOT=yes</code>, it checks whether <span class="application"><strong>NetworkManager</strong></span> is already starting the DEVICE from that <code class="filename">ifcfg</code> file. If <span class="application"><strong>NetworkManager</strong></span> is starting that device or has already started it, nothing more is done for that file, and the next <code class="command">ONBOOT=yes</code> file is checked. If <span class="application"><strong>NetworkManager</strong></span> is not yet starting that device, the initscripts will continue with their traditional behavior and call <code class="filename">ifup</code> for that <code class="filename">ifcfg</code> file.
+ </div><div class="para">
+ The end result is that any <code class="filename">ifcfg</code> file that has <code class="command">ONBOOT=yes</code> is expected to be started on system bootup, either by <span class="application"><strong>NetworkManager</strong></span> or by the initscripts. This ensures that some legacy network types which <span class="application"><strong>NetworkManager</strong></span> does not handle (such as ISDN or analog dialup modems) as well as any new application not yet supported by <span class="application"><strong>NetworkManager</strong></span> are still correctly started by the initscripts even though <span class="application"><strong>NetworkManager</strong></span> is unable to handle them.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ It is recommended not to store backup <code class="filename">ifcfg</code> files in the same location as the live ones. The script literally does <code class="command">ifcfg-*</code> with an exclude only for these extensions: <code class="filename">.old</code>, <code class="filename">.orig</code>, <code class="filename">.rpmnew</code>, <code class="filename">.rpmorig</code>, and <code class="filename">.rpmsave</code>. The best way is not to store backup files anywhere within the <code class="filename">/etc/</code> directory.
+ </div></div></div></div><div class="section" id="sec-Introduction_to_Fedora_Networking-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.8. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding networking for Fedora.
+ </div><div class="section" id="sec-Introduction_to_Fedora_Networking-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.8.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">man(1)</code> man page — Describes man pages and how to find them.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">NetworkManager(8)</code> man page — Describes the network management daemon.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">NetworkManager.conf(5)</code> man page — Describes the <code class="systemitem">NetworkManager</code> configuration file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code>version</code></em>/sysconfig.txt</code> — Describes configuration files and their directives.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-Configure_Networking" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. Configure Networking</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sec-Static_and_Dynamic_Interface_Settings">2.1. Static and Dynamic Interface Settings</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-When_to_Use_Static_Network_Interface_Settings">2.1.1. When to Use Static Network Interface Settings</a></span></dt><dt><span class="section"><a href="#sec-When_to_Use_Dynamic_Interface_Settings">2.1.2. When to Use Dynamic Interface Settings</a></span></dt><dt><span class="section"><a href="#sec-Selecting_Network_Configuration_Methods">2.1.3. Selecting Network Configuration Methods</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface">2.2. Using NetworkManager wi
th the GNOME Graphical User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Connecting_to_a_Network_Using_a_GUI">2.2.1. Connecting to a Network Using a GUI</a></span></dt><dt><span class="section"><a href="#sec-Configuring_New_and_Editing_Existing_Connections">2.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="#sec-Connecting_to_a_Network_Automatically">2.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="#sec-System-wide_and_Private_Connection_Profiles">2.2.4. System-wide and Private Connection Profiles</a></span></dt><dt><span class="section"><a href="#sec-Configuring_a_Wired_Ethernet_Connection">2.2.5. Configuring a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="#sec-Configuring_a_Wi-Fi_Connection">2.2.6. Configuring a Wi-Fi Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_VPN_Connection">2
.2.7. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_Mobile_Broadband_Connection">2.2.8. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_DSL_Connection">2.2.9. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Connection_Settings">2.2.10. Configuring Connection Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_the_Command_Line_Interface">2.3. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configuring_a_Network_Interface_Using_ifcg_Files">2.3.1. Configuring a Network Interface Using ifcfg Files</a></span></dt><dt><span class="section"><a href="#sec-Configuring_a_Network_Interface_Using_ip_commands">2.3.2. Configuring a Network Interface Using ip Commands</a></span></dt><dt><span class="section"><a href="#sec-Static-Routes_and_the_
Default_Gateway">2.3.3. Static Routes and the Default Gateway</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Static_Routes_in_ifcfg_files">2.3.4. Configuring Static Routes in ifcfg files</a></span></dt><dt><span class="section"><a href="#sec-Configuring_IPv6_Tokenized_Interface_Identifiers">2.3.5. Configuring IPv6 Tokenized Interface Identifiers</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_the_NetworkManager_Command_Line_Tool_nmcli">2.4. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Understanding_the_nmcli_Options">2.4.1. Understanding the nmcli Options</a></span></dt><dt><span class="section"><a href="#sec-Connecting_to_a_Network_Using_nmcli">2.4.2. Connecting to a Network Using nmcli</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Static_Routes_Using_nmcli">2.4.3. Configuring Static Routes Using nmcli</a></span></dt></dl></dd><dt><span class="
section"><a href="#sec-Configure_Networking-additional_resources">2.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configure_Networking-docs-inst">2.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-Configure_Networking_Online_Documentation">2.5.2. Online Documentation</a></span></dt></dl></dd></dl></div><div class="section" id="sec-Static_and_Dynamic_Interface_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.1. Static and Dynamic Interface Settings</h2></div></div></div><div class="para">
+ When to use static addressing and when to use dynamic addressing? These decisions are subjective, they depend on your accessed needs, your specific requirements. Having a policy, documenting it, and applying it consistently are usually more important than the specific decisions you make. In a traditional company LAN, this is an easier decision to make as you typically have fewer servers than other hosts. Provisioning and installation tools make providing static configurations to new hosts easy and using such tools will change your work flow and requirements. The following two sections are intended to provide guidance to those who have not already been through this decision-making process. For more information on automated configuration and management, see the <span class="application"><strong>OpenLMI</strong></span> section in the <em class="citetitle">System Administrators Guide</em>. The <em class="citetitle">System Installation Guide</em> documents the use of <span cla
ss="application"><strong>kickstart</strong></span> which can also be used for automating the assignment of network settings.
+ </div><div class="section" id="sec-When_to_Use_Static_Network_Interface_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.1. When to Use Static Network Interface Settings</h3></div></div></div><div class="para">
+
+ </div><div class="para">
+ Use static <code class="systemitem">IP</code> addressing on those servers and devices whose network availability you want to ensure when automatic assignment methods, such as <code class="systemitem">DHCP</code>, fail. <code class="systemitem">DHCP</code>, <code class="systemitem">DNS</code>, and authentication servers are typical examples. Interfaces for out-of-band management devices are also worth configuring with static settings as these devices are supposed to work, as far as is possible, independently of other network infrastructure.
+ </div><div class="para">
+ For hosts which are not considered vital, but for which static <code class="systemitem">IP</code> addressing is still considered desirable, use an automated provisioning method when possible. For example, <code class="systemitem">DHCP</code> servers can be configured to provide the same <code class="systemitem">IP</code> address to the same host every time. This method could be used for communal printers for example.
+ </div><div class="para">
+ All the configuration tools listed in <a class="xref" href="#sec-Selecting_Network_Configuration_Methods">Section 2.1.3, “Selecting Network Configuration Methods”</a> allow assigning static <code class="systemitem">IP</code> addresses manually. The <span class="application"><strong>nmcli</strong></span> tool is also suitable for use with scripted assignment of network configuration.
+ </div></div><div class="section" id="sec-When_to_Use_Dynamic_Interface_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.2. When to Use Dynamic Interface Settings</h3></div></div></div><div class="para">
+
+ </div><div class="para">
+ Enable and use dynamic assignment of <code class="systemitem">IP</code> addresses and other network information whenever there is no compelling reason not to. The time saved in planning and documenting manual settings can be better spent elsewhere. The <em class="firstterm">dynamic host control protocol</em> (<acronym class="acronym">DHCP</acronym>) is a traditional method of dynamically assigning network configurations to hosts. See <a class="xref" href="#sec-dhcp-why">Section 9.1, “Why Use DHCP?”</a> for more information on this subject.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> will by default call the <code class="systemitem">DHCP</code> client, <span class="application"><strong>dhclient</strong></span>, when a profile has been set to obtain addresses automatically, or when an interface configuration file has BOOTPROTO set to <code class="literal">dhcp</code>. Where <code class="systemitem">DHCP</code> is required, an instance of <code class="systemitem">dhclient</code> is started for every Internet protocol, <code class="systemitem">IPv4</code> and <code class="systemitem">IPv6</code>, on an interface. Where <span class="application"><strong>NetworkManager</strong></span> is not running, or not managing an interface, then the legacy network service will call instances of <code class="systemitem">dhclient</code> as required.
+ </div></div><div class="section" id="sec-Selecting_Network_Configuration_Methods"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.3. Selecting Network Configuration Methods</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ To configure a network using graphical user interface tools, proceed to <a class="xref" href="#sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface">Section 2.2, “Using NetworkManager with the GNOME Graphical User Interface”</a>
+ </div></li><li class="listitem"><div class="para">
+ To configure a network interface manually, see <a class="xref" href="#sec-Using_the_Command_Line_Interface">Section 2.3, “Using the Command Line Interface (CLI)”</a>.
+ </div></li><li class="listitem"><div class="para">
+ To configure an interface using <span class="application"><strong>NetworkManager</strong></span>'s command-line tool, <span class="application"><strong>nmcli</strong></span>, proceed to <a class="xref" href="#sec-Using_the_NetworkManager_Command_Line_Tool_nmcli">Section 2.4, “Using the NetworkManager Command Line Tool, nmcli”</a>
+ </div></li></ul></div></div></div><div class="section" id="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Using NetworkManager with the GNOME Graphical User Interface</h2></div></div></div><div class="para">
+ As of <span class="application"><strong>Fedora 20</strong></span>, <span class="application"><strong>NetworkManager</strong></span>'s own graphical user interface (GUI) is not used by default. The <span class="guilabel"><strong>Network</strong></span> settings configuration tool is provided as part of the new GNOME <span class="application"><strong>control-center</strong></span> GUI. The old <span class="application"><strong>nm-connection-editor</strong></span> GUI is still available for certain tasks.
+ </div><div class="section" id="sec-Connecting_to_a_Network_Using_a_GUI"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.1. Connecting to a Network Using a GUI</h3></div></div></div><div class="para">
+ Access the <span class="guilabel"><strong>Network</strong></span> settings window of the <span class="application"><strong>control-center</strong></span> application as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears. Proceed to <a class="xref" href="#sec-Configuring_New_and_Editing_Existing_Connections">Section 2.2.2, “Configuring New and Editing Existing Connections”</a>
+ </div></li></ul></div></div><div class="section" id="sec-Configuring_New_and_Editing_Existing_Connections"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.2. Configuring New and Editing Existing Connections</h3></div></div></div><div class="para">
+ The <span class="guilabel"><strong>Network</strong></span> settings window shows the connection status, its type and interface, its <code class="systemitem">IP</code> address and routing details, and so on.
+ </div><div class="figure" id="exam-Configuring_New_and_Editing_Existing_Connections_Network-Settings-Window"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network-Wired_Gnome3.png"><img src="images/Network-Wired_Gnome3.png" alt="Configure Networks Using the Network Settings Window" /><div class="longdesc"><div class="para">
+ A screen shot of the GNOME control-center Network Settings window. The menu is on the left, the connection status button on the right.
+ </div></div></div></div><h6>Figure 2.1. Configure Networks Using the Network Settings Window</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>Network</strong></span> settings window has a menu on the left-hand side showing the available network devices or interfaces. This includes software interfaces such as for VLANs, bridges, bonds, and teams. On the right-hand side, the <em class="firstterm">connection profiles</em> are shown for the selected network device or interface. A profile is a named collection of settings that can be applied to an interface. Below that is a plus and a minus button for adding and deleting new network connections, and on the right a gear wheel icon will appear for editing the connection details of the selected network device or VPN connection. To add a new connection, click the plus symbol to open the <span class="guilabel"><strong>Add Network Connection</strong></span> window and proceed to <a class="xref" href="#sec-Configuring_a_New_Connection">Section 2.2.2.1, “Configuring a New Connection”</a>.
+ </div><h4 id="bh-Editing_an_Existing_Connection">Editing an Existing Connection</h4><div class="para">
+ Clicking on the gear wheel icon of an existing connection profile in the <span class="guilabel"><strong>Network</strong></span> settings window opens the <span class="guilabel"><strong>Network</strong></span> details window, from where you can perform most network configuration tasks such as <code class="systemitem">IP</code> addressing, <code class="systemitem">DNS</code>, and routing configuration.
+ </div><div class="figure" id="exam-Configuring_New_and_Editing_Existing_Connections_Network-Details-Window"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network-Details-Wired_Gnome3.png"><img src="images/Network-Details-Wired_Gnome3.png" alt="Configure Networks Using the Network Connection Details Window" /><div class="longdesc"><div class="para">
+ A screen shot of GNOME's Network Interface Detail window. The menu is on the left.
+ </div></div></div></div><h6>Figure 2.2. Configure Networks Using the Network Connection Details Window</h6></div><br class="figure-break" /><div class="section" id="sec-Configuring_a_New_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.2.1. Configuring a New Connection</h4></div></div></div><div class="para">
+ In the <span class="guilabel"><strong>Network</strong></span> settings window, click the plus sign below the menu to open the <span class="guilabel"><strong>Add Network Connection</strong></span> window. This displays a list of connection types that can be added.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ VPN connections, click the <span class="guilabel"><strong>VPN</strong></span> entry and proceed to <a class="xref" href="#sec-Establishing_a_VPN_Connection">Section 2.2.7, “Establishing a VPN Connection”</a>;
+ </div></li><li class="listitem"><div class="para">
+ Bond connections, click the <span class="guilabel"><strong>Bond</strong></span> entry and proceed to <a class="xref" href="#sec-Establishing_a_Bond_Connection">Section 4.2.1, “Establishing a Bond Connection”</a>;
+ </div></li><li class="listitem"><div class="para">
+ Bridge connections, click the <span class="guilabel"><strong>Bridge</strong></span> entry and proceed to <a class="xref" href="#sec-Establishing_a_Bridge_Connection">Section 6.1.1, “Establishing a Bridge Connection”</a>;
+ </div></li><li class="listitem"><div class="para">
+ VLAN connections, click the <span class="guilabel"><strong>VLAN</strong></span> entry and proceed to <a class="xref" href="#sec-Establishing_a_VLAN_Connection">Section 7.2.1, “Establishing a VLAN Connection”</a>;or,
+ </div></li><li class="listitem"><div class="para">
+ Team connections, click the <span class="guilabel"><strong>Team</strong></span> entry and proceed to <a class="xref" href="#sec-Creating_a_Network_Team_Using_a_GUI">Section 5.9, “Creating a Network Team Using a GUI”</a>.
+ </div></li></ul></div></div></div><div class="section" id="sec-Connecting_to_a_Network_Automatically"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.3. Connecting to a Network Automatically</h3></div></div></div><div class="para">
+ For any connection type you add or configure, you can choose whether you want <span class="application"><strong>NetworkManager</strong></span> to try to connect to that network automatically when it is available.
+ </div><div class="procedure" id="procedure-Configuring_NetworkManager_to_Connect_to_a_Network_Automatically_When_Detected"><h6>Procedure 2.1. Configuring NetworkManager to Connect to a Network Automatically When Detected</h6><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the network interface from the left-hand-side menu.
+ </div></li><li class="step"><div class="para">
+ Click on the gear wheel icon of a connection profile on the right-hand side menu. If you have only one profile associated with the selected interface the gear wheel icon will be in the lower right-hand-side corner. The <span class="guilabel"><strong>Network</strong></span> details window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Identity</strong></span> menu entry on the left. The <span class="guilabel"><strong>Network</strong></span> window changes to the identity view.
+ </div></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Connect automatically</strong></span> to cause <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the connection whenever <span class="application"><strong>NetworkManager</strong></span> detects that it is available. Clear the check box if you do not want <span class="application"><strong>NetworkManager</strong></span> to connect automatically. If the check box is clear, you will have to select that connection manually in the network settings tool to cause it to connect.
+ </div></li></ol></div></div><div class="section" id="sec-System-wide_and_Private_Connection_Profiles"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.4. System-wide and Private Connection Profiles</h3></div></div></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> stores all <em class="firstterm">connection profiles</em>. A profile is a named collection of settings that can be applied to an interface. <span class="application"><strong>NetworkManager</strong></span> stores these connection profiles for system-wide use (<em class="firstterm">system connections</em>), as well as all <em class="firstterm">user connection</em> profiles. Access to the connection profiles is controlled by permissions which are stored by <span class="application"><strong>NetworkManager</strong></span>. See the <code class="filename">nm-settings(5)</code> man page for more information on the <code class="option">connection</code> settings <code class="option">permissions</code> property. The permissions correspond to the <code class="command">USERS</code> directive in the <code class="filename">ifcfg</code> files. If the <code class="command">USERS</code> directive is not present, the network
profile will be available to all users. As an example, the following command in an <code class="filename">ifcfg</code> file will make the connection available only to the users listed: <pre class="synopsis">USERS="joe bob alice"</pre> This can also be set using graphical user interface tools. In <span class="application"><strong>nm-connection-editor</strong></span>, there is the corresponding <span class="guilabel"><strong>All users may connect to this network</strong></span> check box on the <span class="guilabel"><strong>General</strong></span> tab, and in the GNOME <span class="application"><strong>control-center</strong></span> Network settings Identity window, there is the <span class="guilabel"><strong>Make available to other users</strong></span> check box.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span>'s default policy is to allow all users to create and modify system-wide connections. Profiles that should be available at boot time cannot be private because they will not be visible until the user logs in. For example, if user <code class="systemitem">user</code> creates a connection profile <code class="literal">user-em2</code> with the <span class="guilabel"><strong>Connect Automatically</strong></span> check box selected but with the <span class="guilabel"><strong>Make available to other users</strong></span> not selected, then the connection will not be available at boot time.
+ </div><div class="para">
+ To restrict connections and networking, there are two options which can be used alone or in combination:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Clear the <span class="guilabel"><strong>Make available to other users</strong></span> check box, which changes the connection to be modifiable and usable only by the user doing the changing.
+ </div></li><li class="listitem"><div class="para">
+ Use the <span class="application"><strong>polkit</strong></span> framework to restrict permissions of general network operations on a per-user basis.
+ </div></li></ul></div>
+ The combination of these two options provides fine-grained security and control over networking. See the <code class="filename">polkit(8)</code> man page for more information on <span class="application"><strong>polkit</strong></span>.
+ </div><div class="para">
+ Note that VPN connections are <span class="bold bold"><strong>always</strong></span> created as private-per-user, since they are assumed to be more private than a Wi-Fi or Ethernet connection.
+ </div><div class="procedure"><h6>Procedure 2.2. Changing a Connection to Be User-specific Instead of System-Wide, or Vice Versa</h6><div class="para">
+ Depending on the system's policy, you may need root privileges on the system in order to change whether a connection is user-specific or system-wide.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the network interface from the left-hand-side menu.
+ </div></li><li class="step"><div class="para">
+ Click on the gear wheel icon of a connection profile on the right-hand side menu. If you have only one profile associated with the selected interface the gear wheel icon will be in the lower right-hand-side corner. The <span class="guilabel"><strong>Network</strong></span> details window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Identity</strong></span> menu entry on the left. The <span class="guilabel"><strong>Network</strong></span> window changes to the identity view.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Make available to other users</strong></span> check box to cause <span class="application"><strong>NetworkManager</strong></span> to make the connection available system-wide. Depending on system policy, you may then be prompted for an administrator or <code class="systemitem">root</code> password by the <span class="application"><strong>polkit</strong></span> application. If so, enter the appropriate password to finalize the changes.
+ </div><div class="para">
+ Conversely, clear the <span class="guilabel"><strong>Make available to other users</strong></span> check box to make the connection user-specific.
+ </div></li></ol></div></div><div class="section" id="sec-Configuring_a_Wired_Ethernet_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.5. Configuring a Wired (Ethernet) Connection</h3></div></div></div><div class="para">
+ To configure a wired network connection, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div><div class="para">
+ Select the <span class="guilabel"><strong>Wired</strong></span> network interface from the left-hand-side menu if it is not already highlighted.
+ </div><div class="para">
+ The system creates and configures a single wired <em class="firstterm">connection profile</em> called <span class="guilabel"><strong>Wired</strong></span> by default. A profile is a named collection of settings that can be applied to an interface. More than one profile can be created for an interface and applied as needed. The default profile cannot be deleted but its settings can be changed. You can edit the default <span class="guilabel"><strong>Wired</strong></span> profile by clicking the gear wheel icon. You can create a new wired connection profile by clicking the <span class="guilabel"><strong>Add Profile</strong></span> button. Connection profiles associated with a selected interface are shown on the right-hand side menu.
+ </div><div class="para">
+ When you add a new connection by clicking the <span class="guibutton"><strong>Add Profile</strong></span> button, <span class="application"><strong>NetworkManager</strong></span> creates a new configuration file for that connection and then opens the same dialog that is used for editing an existing connection. The difference between these dialogs is that an existing connection profile has a <span class="guilabel"><strong>Details</strong></span> and <span class="guilabel"><strong>Reset</strong></span> menu entry. In effect, you are always editing a connection profile; the difference only lies in whether that connection previously existed or was just created by <span class="application"><strong>NetworkManager</strong></span> when you clicked <span class="guibutton"><strong>Add Profile</strong></span>.
+ </div><div class="section" id="sec-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-wired"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.5.1. Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4></div></div></div><div class="para">
+ Many settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types, see the <span class="guilabel"><strong>Identity</strong></span> view if using the GNOME tool or the <span class="guilabel"><strong>General</strong></span> tab if using <span class="application"><strong>nm-connection-editor</strong></span>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the menu of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>MAC Address</strong></span> — Select the MAC address of the interface this profile must be applied to.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Cloned Address</strong></span> — If required, enter a different MAC address to use.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>MTU</strong></span> — If required, enter a specific <em class="firstterm">maximum transmission unit</em> (<acronym class="acronym">MTU</acronym>) to use. The MTU value represents the size in bytes of the largest packet that the link-layer will transmit. This value defaults to <code class="constant">1500</code> and does not generally need to be specified or changed.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Firewall Zone</strong></span> — If required, select a different firewall zone to apply. See the <em class="citetitle"><a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/">Red Hat Enterprise Linux 7 Security Guide</a></em> for more information on firewall zones.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect Automatically</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="#sec-Connecting_to_a_Network_Automatically">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Make available to other users</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="#sec-System-wide_and_Private_Connection_Profiles">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to VPN when using this connection</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the selected VPN connection when this connection profile is connected. Select the VPN from the drop-down menu.
+ </div></li></ul></div><h5 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-Wired">Saving Your New (or Modified) Connection and Making Further Configurations</h5><div class="para">
+ Once you have finished editing your wired connection, click the <span class="guibutton"><strong>Apply</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network</strong></span> window and clicking the gear wheel icon to return to the editing dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ port-based Network Access Control (PNAC), click the <span class="guilabel"><strong>802.1X Security</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_802.1X_Security">Section 2.2.10.1, “Configuring 802.1X Security”</a>;
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv6</code> settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv6_Settings">Section 2.2.10.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div></div></div><div class="section" id="sec-Configuring_a_Wi-Fi_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.6. Configuring a Wi-Fi Connection</h3></div></div></div><div class="para">
+ This section explains how to use <span class="application"><strong>NetworkManager</strong></span> to configure a Wi-Fi (also known as wireless or 802.11<em class="replaceable"><code>a/b/g/n</code></em>) connection to an Access Point.
+ </div><div class="para">
+ To configure a mobile broadband (such as 3G) connection, see <a class="xref" href="#sec-Establishing_a_Mobile_Broadband_Connection">Section 2.2.8, “Establishing a Mobile Broadband Connection”</a>.
+ </div><h4 id="bh-Quickly_Connecting_to_an_Available_Access_Point">Quickly Connecting to an Available Access Point</h4><div class="para">
+ The easiest way to connect to an available access point is to click on the network connection icon to activate the network connection, locate the <em class="firstterm">Service Set Identifier</em> (<acronym class="acronym">SSID</acronym>) of the access point in the list of <span class="guilabel"><strong>Wi-Fi</strong></span> networks, and click on it. A padlock symbol indicates the access point requires authentication. If the access point is secured, a dialog prompts you for an authentication key or password.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> tries to auto-detect the type of security used by the access point. If there are multiple possibilities, <span class="application"><strong>NetworkManager</strong></span> guesses the security type and presents it in the <span class="guilabel"><strong>Wi-Fi security</strong></span> drop-down menu. For WPA-PSK security (WPA with a passphrase) no choice is necessary. For WPA Enterprise (802.1X) you have to specifically select the security, because that cannot be auto-detected. If you are unsure, try connecting to each type in turn. Finally, enter the key or passphrase in the <span class="guilabel"><strong>Password</strong></span> field. Certain password types, such as a 40-bit WEP or 128-bit WPA key, are invalid unless they are of a requisite length. The <span class="guilabel"><strong>Connect</strong></span> button will remain inactive until you enter a key of the length required for the selected security type.
To learn more about wireless security, see <a class="xref" href="#sec-Configuring_Wi-Fi_Security">Section 2.2.10.2, “Configuring Wi-Fi Security”</a>.
+ </div><div class="para">
+ If <span class="application"><strong>NetworkManager</strong></span> connects to the access point successfully, the network connection icon will change into a graphical indicator of the wireless connection's signal strength.
+ </div><div class="para">
+ You can also edit the settings for one of these auto-created access point connections just as if you had added it yourself. The <span class="guilabel"><strong>Wi-Fi</strong></span> page of the <span class="guilabel"><strong>Network</strong></span> window has a <span class="guilabel"><strong>History</strong></span> button. Clicking it reveals a list of all the connections you have ever tried to connect to. See <a class="xref" href="#sec-Editing_a_Connection_or_Creating_a_Completely_New_One">Section 2.2.6.2, “Editing a Connection, or Creating a Completely New One”</a>
+ </div><div class="section" id="sec-Connecting_to_a_Hidden_Wi-Fi_Network"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.6.1. Connecting to a Hidden Wi-Fi Network</h4></div></div></div><div class="para">
+ All access points have a <em class="firstterm">Service Set Identifier</em> (<acronym class="acronym">SSID</acronym>) to identify them. However, an access point may be configured not to broadcast its SSID, in which case it is <span class="emphasis"><em>hidden</em></span>, and will not show up in <span class="application"><strong>NetworkManager</strong></span>'s list of <span class="guilabel"><strong>Available</strong></span> networks. You can still connect to a wireless access point that is hiding its SSID as long as you know its SSID, authentication method, and secrets.
+ </div><div class="para">
+ To connect to a hidden wireless network, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> window appears. Select <span class="guilabel"><strong>Wi-Fi</strong></span> from the menu and then select <span class="guilabel"><strong>Connect to Hidden Network</strong></span> to cause a dialog to appear. If you have connected to the hidden network before, use the <span class="guilabel"><strong>Connection</strong></span> drop-down to select it, and click <span class="guibutton"><strong>Connect</strong></span>. If you have not, leave the <span class="guilabel"><strong>Connection</strong></span> drop-down as <span class="guimenuitem"><strong>New</strong></span>, enter the SSID of the hidden network, select its <span class="guilabel"><strong>Wi-Fi security</st
rong></span> method, enter the correct authentication secrets, and click <span class="guibutton"><strong>Connect</strong></span>.
+ </div><div class="para">
+ For more information on wireless security settings, see <a class="xref" href="#sec-Configuring_Wi-Fi_Security">Section 2.2.10.2, “Configuring Wi-Fi Security”</a>.
+ </div></div><div class="section" id="sec-Editing_a_Connection_or_Creating_a_Completely_New_One"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.6.2. Editing a Connection, or Creating a Completely New One</h4></div></div></div><div class="para">
+ You can edit an existing connection that you have tried or succeeded in connecting to in the past by opening the <span class="guilabel"><strong>Wi-Fi</strong></span> page of the <span class="guilabel"><strong>Network</strong></span> dialog and selecting the gear wheel icon to the right of the Wi-Fi connection name. If the network is not currently in range, click <span class="guilabel"><strong>History</strong></span> to display past connections. When you click the gear wheel icon the editing connection dialog appears. The <span class="guilabel"><strong>Details</strong></span> window shows the connection details.
+ </div><div class="para">
+ To configure a new connection whose SSID is in range, first attempt to connect to it by opening the <span class="guilabel"><strong>Network</strong></span> window, selecting the <span class="guilabel"><strong>Wi-Fi</strong></span> menu entry, and clicking the connection name (by default, the same as the SSID). If the SSID is not in range, see <a class="xref" href="#sec-Connecting_to_a_Hidden_Wi-Fi_Network">Section 2.2.6.1, “Connecting to a Hidden Wi-Fi Network”</a>. If the SSID is in range, the procedure is as follows:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Wi-Fi</strong></span> interface from the left-hand-side menu entry.
+ </div></li><li class="step"><div class="para">
+ Click the Wi-Fi connection profile on the right-hand side menu you want to connect to. A padlock symbol indicates a key or password is required.
+ </div></li><li class="step"><div class="para">
+ If requested, enter the authentication details.
+ </div></li></ol></div><h5 id="bh-Configuring_the_SSID-Connect_Behavior_and_Availability_Settings-wireless">Configuring the SSID, Auto-Connect Behavior, and Availability Settings</h5><div class="para">
+ To edit a Wi-Fi connection's settings, select <span class="guilabel"><strong>Wi-Fi</strong></span> in the <span class="guilabel"><strong>Network</strong></span> page and then select the gear wheel icon to the right of the Wi-Fi connection name. Select <span class="guilabel"><strong>Identity</strong></span>. The following settings are available:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>SSID</strong></span> </span></dt><dd><div class="para">
+ The <em class="firstterm">Service Set Identifier</em> (<acronym class="acronym">SSID</acronym>) of the access point (AP).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>BSSID</strong></span> </span></dt><dd><div class="para">
+ The <em class="firstterm">Basic Service Set Identifier</em> (<acronym class="acronym">BSSID</acronym>) is the MAC address, also known as a <em class="firstterm">hardware address</em>, of the specific wireless access point you are connecting to when in <span class="guilabel"><strong>Infrastructure</strong></span> mode. This field is blank by default, and you are able to connect to a wireless access point by <span class="guilabel"><strong>SSID</strong></span> without having to specify its <span class="guilabel"><strong>BSSID</strong></span>. If the BSSID is specified, it will force the system to associate to a specific access point only.
+ </div><div class="para">
+ For ad-hoc networks, the <span class="guilabel"><strong>BSSID</strong></span> is generated randomly by the <span class="application"><strong>mac80211</strong></span> subsystem when the ad-hoc network is created. It is not displayed by <span class="application"><strong>NetworkManager</strong></span>
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>MAC address</strong></span> </span></dt><dd><div class="para">
+ Select the MAC address, also known as a <em class="firstterm">hardware address</em>, of the Wi-Fi interface to use.
+ </div><div class="para">
+ A single system could have one or more wireless network adapters connected to it. The <span class="guilabel"><strong>MAC address</strong></span> field therefore allows you to associate a specific wireless adapter with a specific connection (or connections).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Cloned Address</strong></span> </span></dt><dd><div class="para">
+ A cloned MAC address to use in place of the real hardware address. Leave blank unless required.
+ </div></dd></dl></div><div class="para">
+ The following settings are common to all connection profiles:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="#sec-Connecting_to_a_Network_Automatically">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Make available to other users</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="#sec-System-wide_and_Private_Connection_Profiles">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li></ul></div><h5 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-wireless">Saving Your New (or Modified) Connection and Making Further Configurations</h5><div class="para">
+ Once you have finished editing the wireless connection, click the <span class="guibutton"><strong>Apply</strong></span> button to save your configuration. Given a correct configuration, you can connect to your modified connection by selecting it from the GNOME Shell notification area menu in the top right-hand corner of the screen. Click in the top right-hand side corner to open the menu. Select <span class="guimenuitem"><strong>Wi-Fi</strong></span>. See <a class="xref" href="#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for details on selecting and connecting to a network.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network</strong></span> window and clicking the gear wheel icon to reveal the connection details.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ security authentication for the wireless connection, click <span class="guilabel"><strong>Security</strong></span> and proceed to <a class="xref" href="#sec-Configuring_Wi-Fi_Security">Section 2.2.10.2, “Configuring Wi-Fi Security”</a>;
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click <span class="guilabel"><strong>IPv4</strong></span> and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv6</code> settings for the connection, click <span class="guilabel"><strong>IPv6</strong></span> and proceed to <a class="xref" href="#sec-Configuring_IPv6_Settings">Section 2.2.10.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div></div></div><div class="section" id="sec-Establishing_a_VPN_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.7. Establishing a VPN Connection</h3></div></div></div><div class="para">
+ Establishing a Virtual Private Network (VPN) enables communication between your Local Area Network (LAN), and another, remote LAN. This is done by setting up a tunnel across an intermediate network such as the Internet. The VPN tunnel that is set up typically uses authentication and encryption. After successfully establishing a VPN connection using a secure tunnel, a VPN router or gateway performs the following actions upon the packets you transmit:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ it adds an <em class="firstterm">Authentication Header</em> for routing and authentication purposes;
+ </div></li><li class="listitem"><div class="para">
+ it encrypts the packet data; and,
+ </div></li><li class="listitem"><div class="para">
+ it encloses the data in packets according to the Encapsulating Security Payload (ESP) protocol, which constitutes the decryption and handling instructions.
+ </div></li></ol></div><div class="para">
+ The receiving VPN router strips the header information, decrypts the data, and routes it to its intended destination (either a workstation or other node on a network). Using a network-to-network connection, the receiving node on the local network receives the packets already decrypted and ready for processing. The encryption and decryption process in a network-to-network VPN connection is therefore transparent to clients.
+ </div><div class="para">
+ Because they employ several layers of authentication and encryption, VPNs are a secure and effective means of connecting multiple remote nodes to act as a unified intranet.
+ </div><div class="procedure" id="procedure-Adding_a_New_VPN_Connection"><h6>Procedure 2.3. Adding a New VPN Connection</h6><div class="para">
+ You can configure a new VPN connection by opening the <span class="guilabel"><strong>Network</strong></span> window and selecting the plus symbol below the menu.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the plus symbol below the menu. The <span class="guilabel"><strong>Add Network Connection</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>VPN</strong></span> menu entry. The view now changes to offer configuring a VPN manually, or importing a VPN configuration file.
+ </div><div class="para">
+ The appropriate <span class="application"><strong>NetworkManager</strong></span> VPN plug-in for the VPN type you want to configure must be installed. (see <em class="citetitle">Fedora 20 System Administrator's Guide</em> for more information on how to install new packages in Fedora 20).
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guibutton"><strong>Add</strong></span> button to open the <span class="guilabel"><strong>Choose a VPN Connection Type</strong></span> assistant.
+ </div></li><li class="step"><div class="para">
+ Select the VPN protocol for the gateway you are connecting to from the menu. The VPN protocols available for selection in the menu correspond to the <span class="application"><strong>NetworkManager</strong></span> VPN plug-ins installed. For example, if the <span class="package">NetworkManager-openswan-gnome</span> package is installed then the IPsec based VPN will be selectable from the menu.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Add Network Connection</strong></span> window changes to present the settings customized for the type of VPN connection you selected in the previous step.
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_VPN_Connection"><h6>Procedure 2.4. Editing an Existing VPN Connection</h6><div class="para">
+ You can configure an existing VPN connection by opening the <span class="guilabel"><strong>Network</strong></span> window and selecting the name of the connection from the list. Then click the <span class="guibutton"><strong>Edit</strong></span> button.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>VPN</strong></span> connection you want to edit from the left hand menu.
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guilabel"><strong>Configure</strong></span> button.
+ </div></li></ol></div><h4 id="bh-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-vpn">Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Five settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types, see the <span class="guilabel"><strong>General</strong></span> tab:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the menu of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to this network when it is available</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="#sec-Connecting_to_a_Network_Automatically">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>All users may connect to this network</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="#sec-System-wide_and_Private_Connection_Profiles">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to VPN when using this connection</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to a VPN connection when it is available. Select the VPN from the drop-down menu.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Firewall Zone</strong></span> — Select the Firewall Zone from the dropdown menu.
+ </div></li></ul></div><h4 id="bh-Configuring_the_VPN_Tab">Configuring the VPN Tab</h4><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Gateway</strong></span> </span></dt><dd><div class="para">
+ The name or <code class="systemitem">IP</code> address of the remote VPN gateway.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Group name</strong></span> </span></dt><dd><div class="para">
+ The name of a VPN group configured on the remote gateway.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>User password</strong></span> </span></dt><dd><div class="para">
+ If required, enter the password used to authenticate with the VPN.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Group password</strong></span> </span></dt><dd><div class="para">
+ If required, enter the password used to authenticate with the VPN.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>User name</strong></span> </span></dt><dd><div class="para">
+ If required, enter the user name used to authenticate with the VPN.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Phase1 Algorithms</strong></span> </span></dt><dd><div class="para">
+ If required, enter the algorithms to be used to authenticate and set up an encrypted channel.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Phase2 Algorithms</strong></span> </span></dt><dd><div class="para">
+ If required, enter the algorithms to be used for the IPsec negotiations.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Domain</strong></span> </span></dt><dd><div class="para">
+ If required, enter the Domain Name.
+ </div></dd></dl></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-vpn">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your new VPN connection, click the <span class="guibutton"><strong>Save</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network</strong></span> window and clicking <span class="guilabel"><strong>Configure</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>.
+ </div></li></ul></div></div><div class="section" id="sec-Establishing_a_Mobile_Broadband_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.8. Establishing a Mobile Broadband Connection</h3></div></div></div><div class="para">
+ You can use <span class="application"><strong>NetworkManager</strong></span>'s mobile broadband connection abilities to connect to the following <em class="firstterm">2G</em> and <em class="firstterm">3G</em> services:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 2G — <em class="firstterm">GPRS</em> (<em class="firstterm">General Packet Radio Service</em>), <em class="firstterm">EDGE</em> (<em class="firstterm">Enhanced Data Rates for GSM Evolution</em>), or CDMA (Code Division Multiple Access).
+ </div></li><li class="listitem"><div class="para">
+ 3G — <em class="firstterm">UMTS</em> (<em class="firstterm">Universal Mobile Telecommunications System</em>), <em class="firstterm">HSPA</em> (<em class="firstterm">High Speed Packet Access</em>), or EVDO (EVolution Data-Only).
+ </div></li></ul></div><div class="para">
+ Your computer must have a mobile broadband device (modem), which the system has discovered and recognized, in order to create the connection. Such a device may be built into your computer (as is the case on many notebooks and netbooks), or may be provided separately as internal or external hardware. Examples include PC card, USB Modem or Dongle, mobile or cellular telephone capable of acting as a modem.
+ </div><div class="procedure" id="procedure-Adding_a_New_Mobile_Broadband_Connection"><h6>Procedure 2.5. Adding a New Mobile Broadband Connection</h6><div class="para">
+ You can configure a mobile broadband connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> tool and selecting the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">nm-connection-editor</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network Connections</strong></span> tool appears.
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guibutton"><strong>Add</strong></span> button. The <span class="guilabel"><strong>Choose a Connection Type</strong></span> menu opens.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guimenu"><strong>Mobile Broadband</strong></span> menu entry.
+ </div></li><li class="step"><div class="para">
+ Click <span class="guibutton"><strong>Create</strong></span> to open the <span class="guilabel"><strong>Set up a Mobile Broadband Connection</strong></span> assistant.
+ </div></li><li class="step"><div class="para">
+ Under <span class="guilabel"><strong>Create a connection for this mobile broadband device</strong></span>, choose the 2G- or 3G-capable device you want to use with the connection. If the drop-down menu is inactive, this indicates that the system was unable to detect a device capable of mobile broadband. In this case, click <span class="guilabel"><strong>Cancel</strong></span>, ensure that you do have a mobile broadband-capable device attached and recognized by the computer and then retry this procedure. Click the <span class="guilabel"><strong>Continue</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select the country where your service provider is located from the list and click the <span class="guilabel"><strong>Continue</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select your provider from the list or enter it manually. Click the <span class="guilabel"><strong>Continue</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select your payment plan from the drop-down menu and confirm the <em class="firstterm">Access Point Name</em> (<acronym class="acronym">APN</acronym>) is correct. Click the <span class="guilabel"><strong>Continue</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Review and confirm the settings and then click the <span class="guilabel"><strong>Apply</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Edit the mobile broadband-specific settings by referring to <a class="xref" href="#sec-Configuring_the_Mobile_Broadband_Tab">Section 2.2.8.1, “Configuring the Mobile Broadband Tab”</a>.
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_Mobile_Broadband_Connection"><h6>Procedure 2.6. Editing an Existing Mobile Broadband Connection</h6><div class="para">
+ Follow these steps to edit an existing mobile broadband connection.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">nm-connection-editor</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network Connections</strong></span> tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Select the connection you want to edit and click the <span class="guilabel"><strong>Edit</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Configure the connection name, auto-connect behavior, and availability settings.
+ </div><div class="para">
+ Five settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types, see the <span class="guilabel"><strong>General</strong></span> tab:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the menu of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to this network when it is available</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="#sec-Connecting_to_a_Network_Automatically">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>All users may connect to this network</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="#sec-System-wide_and_Private_Connection_Profiles">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to VPN when using this connection</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to a VPN connection when it is available. Select the VPN from the drop-down menu.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Firewall Zone</strong></span> — Select the Firewall Zone from the drop-down menu.
+ </div></li></ul></div></li><li class="step"><div class="para">
+ Edit the mobile broadband-specific settings by referring to <a class="xref" href="#sec-Configuring_the_Mobile_Broadband_Tab">Section 2.2.8.1, “Configuring the Mobile Broadband Tab”</a>.
+ </div></li></ol></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-mobile_broadband">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your mobile broadband connection, click the <span class="guibutton"><strong>Apply</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Point-to-point</strong></span> settings for the connection, click the <span class="guilabel"><strong>PPP Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_PPP_Point-to-Point_Settings">Section 2.2.10.3, “Configuring PPP (Point-to-Point) Settings”</a>;
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv6</code> settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv6_Settings">Section 2.2.10.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div><div class="section" id="sec-Configuring_the_Mobile_Broadband_Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.8.1. Configuring the Mobile Broadband Tab</h4></div></div></div><div class="para">
+ If you have already added a new mobile broadband connection using the assistant (see <a class="xref" href="#procedure-Adding_a_New_Mobile_Broadband_Connection">Procedure 2.5, “Adding a New Mobile Broadband Connection”</a> for instructions), you can edit the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab to disable roaming if home network is not available, assign a network ID, or instruct <span class="application"><strong>NetworkManager</strong></span> to prefer a certain technology (such as 3G or 2G) when using the connection.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Number</strong></span> </span></dt><dd><div class="para">
+ The number that is dialed to establish a PPP connection with the GSM-based mobile broadband network. This field may be automatically populated during the initial installation of the broadband device. You can usually leave this field blank and enter the <span class="guilabel"><strong>APN</strong></span> instead.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the user name used to authenticate with the network. Some providers do not provide a user name, or accept any user name when connecting to the network.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password used to authenticate with the network. Some providers do not provide a password, or accept any password.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>APN</strong></span> </span></dt><dd><div class="para">
+ Enter the <em class="firstterm">Access Point Name</em> (<acronym class="acronym">APN</acronym>) used to establish a connection with the GSM-based network. Entering the correct APN for a connection is important because it often determines:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ how the user is billed for their network usage; and/or
+ </div></li><li class="listitem"><div class="para">
+ whether the user has access to the Internet, an intranet, or a subnetwork.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Network ID</strong></span> </span></dt><dd><div class="para">
+ Entering a <span class="guilabel"><strong>Network ID</strong></span> causes <span class="application"><strong>NetworkManager</strong></span> to force the device to register only to a specific network. This can be used to ensure the connection does not roam when it is not possible to control roaming directly.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Type</strong></span> </span></dt><dd><div class="para">
+ <span class="guilabel"><strong>Any</strong></span> — The default value of <span class="guilabel"><strong>Any</strong></span> leaves the modem to select the fastest network.
+ </div><div class="para">
+ <span class="guilabel"><strong>3G (UMTS/HSPA)</strong></span> — Force the connection to use only 3G network technologies.
+ </div><div class="para">
+ <span class="guilabel"><strong>2G (GPRS/EDGE)</strong></span> — Force the connection to use only 2G network technologies.
+ </div><div class="para">
+ <span class="guilabel"><strong>Prefer 3G (UMTS/HSPA)</strong></span> — First attempt to connect using a 3G technology such as HSPA or UMTS, and fall back to GPRS or EDGE only upon failure.
+ </div><div class="para">
+ <span class="guilabel"><strong>Prefer 2G (GPRS/EDGE)</strong></span> — First attempt to connect using a 2G technology such as GPRS or EDGE, and fall back to HSPA or UMTS only upon failure.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Allow roaming if home network is not available</strong></span> </span></dt><dd><div class="para">
+ Uncheck this box if you want <span class="application"><strong>NetworkManager</strong></span> to terminate the connection rather than transition from the home network to a roaming one, thereby avoiding possible roaming charges. If the box is checked, <span class="application"><strong>NetworkManager</strong></span> will attempt to maintain a good connection by transitioning from the home network to a roaming one, and vice versa.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>PIN</strong></span> </span></dt><dd><div class="para">
+ If your device's <em class="firstterm">SIM</em> (<em class="firstterm">Subscriber Identity Module</em>) is locked with a <em class="firstterm">PIN</em> (<em class="firstterm">Personal Identification Number</em>), enter the PIN so that <span class="application"><strong>NetworkManager</strong></span> can unlock the device. <span class="application"><strong>NetworkManager</strong></span> must unlock the SIM if a PIN is required in order to use the device for any purpose.
+ </div></dd></dl></div><div class="para">
+ CDMA and EVDO have fewer options. They do not have the <code class="option">APN</code>, <code class="option">Network ID</code>, or <code class="option">Type</code> options.
+ </div></div></div><div class="section" id="sec-Establishing_a_DSL_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.9. Establishing a DSL Connection</h3></div></div></div><div class="para">
+ This section is intended for those installations which have a DSL card fitted within a host rather than the external combined DSL modem router combinations typical of private consumer or SOHO installations.
+ </div><div class="procedure" id="procedure-Adding_a_New_DSL_Connection"><h6>Procedure 2.7. Adding a New DSL Connection</h6><div class="para">
+ You can configure a new DSL connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> window, clicking the <span class="guibutton"><strong>Add</strong></span> button and selecting <span class="guilabel"><strong>DSL</strong></span> from the <span class="guilabel"><strong>Hardware</strong></span> section of the new connection list.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">nm-connection-editor</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network Connections</strong></span> tool appears.
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guibutton"><strong>Add</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Choose a Connection Type</strong></span> list appears.
+ </div></li><li class="step"><div class="para">
+ Select <span class="guimenu"><strong>DSL</strong></span> and press the <span class="guibutton"><strong>Create</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Editing DSL Connection <em class="replaceable"><code>1</code></em></strong></span> window appears.
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_DSL_Connection"><h6>Procedure 2.8. Editing an Existing DSL Connection</h6><div class="para">
+ You can configure an existing DSL connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> window and selecting the name of the connection from the list. Then click the <span class="guibutton"><strong>Edit</strong></span> button.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">nm-connection-editor</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network Connections</strong></span> tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the connection you want to edit and click the <span class="guilabel"><strong>Edit</strong></span> button.
+ </div></li></ol></div><h4 id="bh-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-dsl">Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Five settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types, see the <span class="guilabel"><strong>General</strong></span> tab:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the menu of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to this network when it is available</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="#sec-Connecting_to_a_Network_Automatically">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>All users may connect to this network</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="#sec-System-wide_and_Private_Connection_Profiles">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to VPN when using this connection</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to a VPN connection when it is available. Select the VPN from the drop-down menu.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Firewall Zone</strong></span> — Select the Firewall Zone from the drop-down menu.
+ </div></li></ul></div><h4 id="bh-Configuring_the_DSL_Tab">Configuring the DSL Tab</h4><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the user name used to authenticate with the service provider.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Service</strong></span> </span></dt><dd><div class="para">
+ Leave blank unless otherwise directed by your service provider.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password supplied by the service provider.
+ </div></dd></dl></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-DSL">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your DSL connection, click the <span class="guibutton"><strong>Apply</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>The MAC address and MTU</strong></span> settings, click the <span class="guilabel"><strong>Wired</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-wired">Section 2.2.5.1, “Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings”</a>;
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Point-to-point</strong></span> settings for the connection, click the <span class="guilabel"><strong>PPP Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_PPP_Point-to-Point_Settings">Section 2.2.10.3, “Configuring PPP (Point-to-Point) Settings”</a>;
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>.
+ </div></li></ul></div></div><div class="section" id="sec-Configuring_Connection_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.10. Configuring Connection Settings</h3></div></div></div><div class="section" id="sec-Configuring_802.1X_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.10.1. Configuring 802.1X Security</h4></div></div></div><div class="para">
+ 802.1X security is the name of the IEEE standard for <em class="firstterm">port-based Network Access Control</em> (<acronym class="acronym">PNAC</acronym>). It is also called <em class="firstterm">WPA Enterprise</em>. Simply put, 802.1X security is a way of controlling access to a <em class="firstterm">logical network</em> from a physical one. All clients who want to join the logical network must authenticate with the server (a router, for example) using the correct 802.1X authentication method.
+ </div><div class="para">
+ 802.1X security is most often associated with securing wireless networks (WLANs), but can also be used to prevent intruders with physical access to the network (LAN) from gaining entry. In the past, <code class="systemitem">DHCP</code> servers were configured not to lease <code class="systemitem">IP</code> addresses to unauthorized users, but for various reasons this practice is both impractical and insecure, and thus is no longer recommended. Instead, 802.1X security is used to ensure a logically-secure network through port-based authentication.
+ </div><div class="para">
+ 802.1X provides a framework for WLAN and LAN access control and serves as an envelope for carrying one of the Extensible Authentication Protocol (EAP) types. An EAP type is a protocol that defines how security is achieved on the network.
+ </div><div class="para">
+ You can configure 802.1X security for a wired or wireless connection type by opening the <span class="guilabel"><strong>Network</strong></span> window (see <a class="xref" href="#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a>) and following the applicable procedure below. Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears. Proceed to <a class="xref" href="#procedure-For_a_Wired_Connection">Procedure 2.9, “For a Wired Connection”</a> or <a class="xref" href="#procedure-For_a_Wireless_Connection">Procedure 2.10, “For a Wireless Connection”</a>:
+ </div><div class="procedure" id="procedure-For_a_Wired_Connection"><h6>Procedure 2.9. For a Wired Connection</h6><ol class="1"><li class="step"><div class="para">
+ Select a <span class="guilabel"><strong>Wired</strong></span> network interface from the left-hand-side menu.
+ </div></li><li class="step"><div class="para">
+ Either click on <span class="guibutton"><strong>Add Profile</strong></span> to add a new network connection profile for which you want to configure 802.1X security, or select an existing connection profile and click the gear wheel icon.
+ </div></li><li class="step"><div class="para">
+ Then select <span class="guilabel"><strong>Security</strong></span> and set the symbolic power button to <span class="guilabel"><strong>ON</strong></span> to enable settings configuration.
+ </div></li><li class="step"><div class="para">
+ Proceed to <a class="xref" href="#sec-Configuring_TLS_Transport_Layer_Security_Settings">Section 2.2.10.1.1, “Configuring TLS (Transport Layer Security) Settings”</a>
+ </div></li></ol></div><div class="procedure" id="procedure-For_a_Wireless_Connection"><h6>Procedure 2.10. For a Wireless Connection</h6><ol class="1"><li class="step"><div class="para">
+ Select a <span class="guilabel"><strong>Wireless</strong></span> network interface from the left-hand-side menu. If necessary, set the symbolic power button to <span class="guilabel"><strong>ON</strong></span> and check that your hardware switch is on.
+ </div></li><li class="step"><div class="para">
+ Either select the connection name of a new connection, or click the gear wheel icon of an existing connection profile, for which you want to configure 802.1X security. In the case of a new connection, complete any authentication steps to complete the connection and then click the gear wheel icon.
+ </div></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Security</strong></span>.
+ </div></li><li class="step"><div class="para">
+ From the drop-down menu select one of the following security methods: <span class="guimenuitem"><strong>LEAP</strong></span>, <span class="guimenuitem"><strong>Dynamic WEP (802.1X)</strong></span>, or <span class="guimenuitem"><strong>WPA & WPA2 Enterprise</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Refer to <a class="xref" href="#sec-Configuring_TLS_Transport_Layer_Security_Settings">Section 2.2.10.1.1, “Configuring TLS (Transport Layer Security) Settings”</a> for descriptions of which <em class="firstterm">extensible authentication protocol</em> (<acronym class="acronym">EAP</acronym>) types correspond to your selection in the <span class="guilabel"><strong>Security</strong></span> drop-down menu.
+ </div></li></ol></div><div class="section" id="sec-Configuring_TLS_Transport_Layer_Security_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.10.1.1. Configuring TLS (Transport Layer Security) Settings</h5></div></div></div><div class="para">
+ With Transport Layer Security, the client and server mutually authenticate using the TLS protocol. The server demonstrates that it holds a digital certificate, the client proves its own identity using its client-side certificate, and key information is exchanged. Once authentication is complete, the TLS tunnel is no longer used. Instead, the client and server use the exchanged keys to encrypt data using AES, TKIP or WEP.
+ </div><div class="para">
+ The fact that certificates must be distributed to all clients who want to authenticate means that the EAP-TLS authentication method is very strong, but also more complicated to set up. Using TLS security requires the overhead of a public key infrastructure (PKI) to manage certificates. The benefit of using TLS security is that a compromised password does not allow access to the (W)LAN: an intruder must also have access to the authenticating client's private key.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> does not determine the version of TLS supported. <span class="application"><strong>NetworkManager</strong></span> gathers the parameters entered by the user and passes them to the daemon, <span class="application"><strong>wpa_supplicant</strong></span>, that handles the procedure. It in turn uses OpenSSL to establish the TLS tunnel. OpenSSL itself negotiates the SSL/TLS protocol version. It uses the highest version both ends support.
+ </div><h6 id="Selecting_an_Authentication_Method">Selecting an Authentication Method</h6><div class="para">
+ Select from one of following authentication methods:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Select <span class="guilabel"><strong>TLS</strong></span> for <em class="firstterm">Transport Layer Security</em> and proceed to <a class="xref" href="#sec-Configuring_TLS_Settings">Section 2.2.10.1.2, “Configuring TLS Settings”</a>;
+ </div></li><li class="listitem"><div class="para">
+ Select <span class="guilabel"><strong>FAST</strong></span> for <em class="firstterm">Flexible Authentication via Secure Tunneling</em> and proceed to <a class="xref" href="#sec-Configuring_Tunneled_TLS_Settings">Section 2.2.10.1.4, “Configuring Tunneled TLS Settings”</a>;
+ </div></li><li class="listitem"><div class="para">
+ Select <span class="guilabel"><strong>Tunneled TLS</strong></span> for <em class="firstterm">Tunneled Transport Layer Security</em>, otherwise known as TTLS, or EAP-TTLS and proceed to <a class="xref" href="#sec-Configuring_Tunneled_TLS_Settings">Section 2.2.10.1.4, “Configuring Tunneled TLS Settings”</a>;
+ </div></li><li class="listitem"><div class="para">
+ Select <span class="guilabel"><strong>Protected EAP (PEAP)</strong></span> for <em class="firstterm">Protected Extensible Authentication Protocol</em> and proceed to <a class="xref" href="#sec-Configuring_Protected_EAP_PEAP_Settings">Section 2.2.10.1.5, “Configuring Protected EAP (PEAP) Settings”</a>.
+ </div></li></ul></div></div><div class="section" id="sec-Configuring_TLS_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.10.1.2. Configuring TLS Settings</h5></div></div></div><div class="para">
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Identity</strong></span> </span></dt><dd><div class="para">
+ Provide the identity of this server.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>User certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a personal X.509 certificate file encoded with <em class="firstterm">Distinguished Encoding Rules</em> (<acronym class="acronym">DER</acronym>) or <em class="firstterm">Privacy Enhanced Mail</em> (<acronym class="acronym">PEM</acronym>).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, an X.509 <em class="firstterm">certificate authority</em> certificate file encoded with <em class="firstterm">Distinguished Encoding Rules</em> (<acronym class="acronym">DER</acronym>) or <em class="firstterm">Privacy Enhanced Mail</em> (<acronym class="acronym">PEM</acronym>).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Private key</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a <em class="firstterm">private key</em> file encoded with <em class="firstterm">Distinguished Encoding Rules</em> (<acronym class="acronym">DER</acronym>), <em class="firstterm">Privacy Enhanced Mail</em> (<acronym class="acronym">PEM</acronym>), or the <em class="firstterm">Personal Information Exchange Syntax Standard</em> (<acronym class="acronym">PKCS #12</acronym>).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Private key password</strong></span> </span></dt><dd><div class="para">
+ Enter the password for the private key in the <span class="guilabel"><strong>Private key</strong></span> field. Select <span class="guilabel"><strong>Show password</strong></span> to make the password visible as you type it.
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_FAST_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.10.1.3. Configuring FAST Settings</h5></div></div></div><div class="para">
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Anonymous Identity</strong></span> </span></dt><dd><div class="para">
+ Provide the identity of this server.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>PAC provisioning</strong></span> </span></dt><dd><div class="para">
+ Select the check box to enable and then select from <span class="guimenu"><strong>Anonymous</strong></span>, <span class="guimenu"><strong>Authenticated</strong></span>, and <span class="guimenu"><strong>Both</strong></span>.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>PAC file</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a <em class="firstterm">protected access credential</em> (<acronym class="acronym">PAC</acronym>) file.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Inner authentication</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>GTC</strong></span> — Generic Token Card.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MSCHAPv2</strong></span> — Microsoft Challenge Handshake Authentication Protocol version 2.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the user name to be used in the authentication process.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password to be used in the authentication process.
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_Tunneled_TLS_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.10.1.4. Configuring Tunneled TLS Settings</h5></div></div></div><div class="para">
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Anonymous identity</strong></span> </span></dt><dd><div class="para">
+ This value is used as the unencrypted identity.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a Certificate Authority's certificate.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Inner authentication</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>PAP</strong></span> — Password Authentication Protocol.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MSCHAP</strong></span> — Challenge Handshake Authentication Protocol.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MSCHAPv2</strong></span> — Microsoft Challenge Handshake Authentication Protocol version 2.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>CHAP</strong></span> — Challenge Handshake Authentication Protocol.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the user name to be used in the authentication process.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password to be used in the authentication process.
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_Protected_EAP_PEAP_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.10.1.5. Configuring Protected EAP (PEAP) Settings</h5></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Anonymous Identity</strong></span> </span></dt><dd><div class="para">
+ This value is used as the unencrypted identity.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a Certificate Authority's certificate.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>PEAP version</strong></span> </span></dt><dd><div class="para">
+ The version of Protected EAP to use. Automatic, 0 or 1.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Inner authentication</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>MSCHAPv2</strong></span> — Microsoft Challenge Handshake Authentication Protocol version 2.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MD5</strong></span> — Message Digest 5, a cryptographic hash function.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>GTC</strong></span> — Generic Token Card.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the user name to be used in the authentication process.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password to be used in the authentication process.
+ </div></dd></dl></div></div></div><div class="section" id="sec-Configuring_Wi-Fi_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.10.2. Configuring Wi-Fi Security</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Security</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>None</strong></span> — Do not encrypt the Wi-Fi connection.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WEP 40/128-bit Key</strong></span> — Wired Equivalent Privacy (WEP), from the IEEE 802.11 standard. Uses a single pre-shared key (PSK).
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WEP 128-bit Passphrase</strong></span> — An MD5 hash of the passphrase will be used to derive a WEP key.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>LEAP</strong></span> — Lightweight Extensible Authentication Protocol, from Cisco Systems.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Dynamic WEP (802.1X)</strong></span> — WEP keys are changed dynamically. Use with <a class="xref" href="#sec-Configuring_TLS_Transport_Layer_Security_Settings">Section 2.2.10.1.1, “Configuring TLS (Transport Layer Security) Settings”</a>
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WPA & WPA2 Personal</strong></span> — Wi-Fi Protected Access (WPA), from the draft IEEE 802.11i standard. A replacement for WEP. Wi-Fi Protected Access II (WPA2), from the 802.11i-2004 standard. Personal mode uses a pre-shared key (WPA-PSK).
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WPA & WPA2 Enterprise</strong></span> — WPA for use with a RADIUS authentication server to provide IEEE 802.1X network access control. Use with <a class="xref" href="#sec-Configuring_TLS_Transport_Layer_Security_Settings">Section 2.2.10.1.1, “Configuring TLS (Transport Layer Security) Settings”</a>
+ </div></dd><dt class="varlistentry"><span class="term">Password</span></dt><dd><div class="para">
+ Enter the password to be used in the authentication process.
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_PPP_Point-to-Point_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.10.3. Configuring PPP (Point-to-Point) Settings</h4></div></div></div><div class="para">
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Configure Methods</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Use point-to-point encryption (MPPE)</strong></span> </span></dt><dd><div class="para">
+ Microsoft Point-To-Point Encryption protocol (<a href="http://www.rfc-editor.org/info/rfc3078"><em class="citetitle">RFC 3078</em></a>).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Allow BSD data compression</strong></span> </span></dt><dd><div class="para">
+ PPP BSD Compression Protocol (<a href="http://www.rfc-editor.org/info/rfc1977"><em class="citetitle">RFC 1977</em></a>).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Allow Deflate data compression</strong></span> </span></dt><dd><div class="para">
+ PPP Deflate Protocol (<a href="http://www.rfc-editor.org/info/rfc1979"><em class="citetitle">RFC 1979</em></a>).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Use TCP header compression</strong></span> </span></dt><dd><div class="para">
+ Compressing TCP/IP Headers for Low-Speed Serial Links (<a href="http://www.rfc-editor.org/info/rfc1144"><em class="citetitle">RFC 1144</em></a>).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Send PPP echo packets</strong></span> </span></dt><dd><div class="para">
+ LCP Echo-Request and Echo-Reply Codes for loopback tests (<a href="http://www.rfc-editor.org/info/rfc1661"><em class="citetitle">RFC 1661</em></a>).
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_IPv4_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.10.4. Configuring IPv4 Settings</h4></div></div></div><div class="para">
+ The <span class="guilabel"><strong>IPv4 Settings</strong></span> tab allows you to configure the method used to connect to a network, to enter <code class="systemitem">IP</code> address, route, and <code class="systemitem">DNS</code> information as required. The <span class="guilabel"><strong>IPv4 Settings</strong></span> tab is available when you create and modify one of the following connection types: wired, wireless, mobile broadband, VPN or DSL. If you need to configure <code class="systemitem">IPv6</code> addresses, see <a class="xref" href="#sec-Configuring_IPv6_Settings">Section 2.2.10.5, “Configuring IPv6 Settings”</a>. If you need to configure static routes, click the <span class="guibutton"><strong>Routes</strong></span> button and proceed to <a class="xref" href="#sec-Configuring_Routes">Section 2.2.10.6, “Configuring Routes”</a>.
+ </div><div class="para">
+ If you are using <code class="systemitem">DHCP</code> to obtain a dynamic <code class="systemitem">IP</code> address from a <code class="systemitem">DHCP</code> server, you can simply set <span class="guilabel"><strong>Method</strong></span> to <span class="guimenuitem"><strong>Automatic (DHCP)</strong></span>.
+ </div><h5 id="bh-Setting_the_Method">Setting the Method</h5><div class="variablelist" id="varlist-Available_IPv4_Methods_by_Connection_Type"><h6>Available IPv4 Methods by Connection Type</h6><div class="para">
+ When you click the <span class="guilabel"><strong>Method</strong></span> drop-down menu, depending on the type of connection you are configuring, you are able to select one of the following <code class="systemitem">IPv4</code> connection methods. All of the methods are listed here according to which connection type, or types, they are associated with:
+ </div><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Method</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (DHCP)</strong></span> — Choose this option if the network you are connecting to uses a <code class="systemitem">DHCP</code> server to assign <code class="systemitem">IP</code> addresses. You do not need to fill in the <span class="guilabel"><strong>DHCP client ID</strong></span> field.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (DHCP) addresses only</strong></span> — Choose this option if the network you are connecting to uses a <code class="systemitem">DHCP</code> server to assign <code class="systemitem">IP</code> addresses but you want to assign <code class="systemitem">DNS</code> servers manually.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Link-Local Only</strong></span> — Choose this option if the network you are connecting to does not have a <code class="systemitem">DHCP</code> server and you do not want to assign <code class="systemitem">IP</code> addresses manually. Random addresses will be assigned as per <a href="http://www.rfc-editor.org/info/rfc3927"><em class="citetitle">RFC 3927</em></a> with prefix <code class="systemitem">169.254/16</code>.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Shared to other computers</strong></span> — Choose this option if the interface you are configuring is for sharing an Internet or WAN connection. The interface is assigned an address in the <code class="systemitem">10.42.x.1/24</code> range, a <code class="systemitem">DHCP</code> server and <code class="systemitem">DNS</code> server are started, and the interface is connected to the default network connection on the system with <em class="firstterm">network address translation</em> (<acronym class="acronym">NAT</acronym>).
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Disabled</strong></span> — <code class="systemitem">IPv4</code> is disabled for this connection.
+ </div></dd><dt class="varlistentry"><span class="term">Wired, Wireless and DSL Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Manual</strong></span> — Choose this option if you want to assign <code class="systemitem">IP</code> addresses manually.
+ </div></dd><dt class="varlistentry"><span class="term">Mobile Broadband Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPP)</strong></span> — Choose this option if the network you are connecting to assigns your <code class="systemitem">IP</code> address and <code class="systemitem">DNS</code> servers automatically.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPP) addresses only</strong></span> — Choose this option if the network you are connecting to assigns your <code class="systemitem">IP</code> address automatically, but you want to manually specify <code class="systemitem">DNS</code> servers.
+ </div></dd><dt class="varlistentry"><span class="term">VPN Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (VPN)</strong></span> — Choose this option if the network you are connecting to assigns your <code class="systemitem">IP</code> address and <code class="systemitem">DNS</code> servers automatically.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (VPN) addresses only</strong></span> — Choose this option if the network you are connecting to assigns your <code class="systemitem">IP</code> address automatically, but you want to manually specify <code class="systemitem">DNS</code> servers.
+ </div></dd><dt class="varlistentry"><span class="term">DSL Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPPoE)</strong></span> — Choose this option if the network you are connecting to assigns your <code class="systemitem">IP</code> address and <code class="systemitem">DNS</code> servers automatically.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPPoE) addresses only</strong></span> — Choose this option if the network you are connecting to assigns your <code class="systemitem">IP</code> address automatically, but you want to manually specify <code class="systemitem">DNS</code> servers.
+ </div></dd></dl></div><div class="para">
+ For information on configuring static routes for the network connection, go to <a class="xref" href="#sec-Configuring_Routes">Section 2.2.10.6, “Configuring Routes”</a>.
+ </div></div><div class="section" id="sec-Configuring_IPv6_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.10.5. Configuring IPv6 Settings</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Method</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Ignore</strong></span> — Choose this option if you want to ignore <code class="systemitem">IPv6</code> settings for this connection.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic</strong></span> — Choose this option to use <em class="firstterm">SLAAC</em> to create an automatic, stateless configuration based on the hardware address and <em class="firstterm">router advertisements</em> (RA).
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic, addresses only</strong></span> — Choose this option if the network you are connecting to uses <em class="firstterm">router advertisements</em> (RA) to create an automatic, stateless configuration, but you want to assign <code class="systemitem">DNS</code> servers manually.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic, DHCP only</strong></span> — Choose this option to not use RA, but request information from <code class="systemitem">DHCPv6</code> directly to create a stateful configuration.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Manual</strong></span> — Choose this option if you want to assign <code class="systemitem">IP</code> addresses manually.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Link-Local Only</strong></span> — Choose this option if the network you are connecting to does not have a <code class="systemitem">DHCP</code> server and you do not want to assign <code class="systemitem">IP</code> addresses manually. Random addresses will be assigned as per <a href="http://www.rfc-editor.org/info/rfc4862"><em class="citetitle">RFC 4862</em></a> with prefix <code class="systemitem">FE80::0</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Addresses</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>DNS servers</strong></span> — Enter a comma separated list of <code class="systemitem">DNS</code> servers.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Search domains</strong></span> — Enter a comma separated list of domain controllers.
+ </div></dd></dl></div><div class="para">
+ For information on configuring static routes for the network connection, go to <a class="xref" href="#sec-Configuring_Routes">Section 2.2.10.6, “Configuring Routes”</a>.
+ </div></div><div class="section" id="sec-Configuring_Routes"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.10.6. Configuring Routes</h4></div></div></div><div class="para">
+ A host's routing table will be automatically populated with routes to directly connected networks. The routes are learned by examining the network interfaces when they are <span class="quote">“<span class="quote">up</span>”</span>. This section describes entering static routes to networks or hosts which can be reached by traversing an intermediate network or connection, such as a VPN tunnel or leased line. In order to reach a remote network or host, the system is given the address of a gateway to which traffic should be sent.
+ </div><div class="para">
+ When a host's interface is configured by <code class="systemitem">DHCP</code>, an address of a gateway that leads to an upstream network or the Internet is usually assigned. This gateway is usually referred to as the default gateway as it is the gateway to use if no better route is known to the system (and present in the routing table). Network administrators often use the first or last host <code class="systemitem">IP</code> address in the network as the gateway address; for example, <code class="systemitem">192.168.10.1</code> or <code class="systemitem">192.168.10.254</code>. Not to be confused by the address which represents the network itself; in this example, <code class="systemitem">192.168.10.0</code>, or the subnet's broadcast address; in this example <code class="systemitem">192.168.10.255</code>.
+ </div><h5 id="Configuring_Static_Routes">Configuring Static Routes</h5><div class="para">
+ To set a static route, open the <span class="guimenu"><strong>IPv4</strong></span> or <span class="guimenu"><strong>IPv6</strong></span> settings window for the connection you want to configure. See <a class="xref" href="#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for instructions on how to do that.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Routes</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Address</strong></span> — Enter the <code class="systemitem">IP</code> address of a remote network, sub-net, or host.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Netmask</strong></span> — The netmask or prefix length of the <code class="systemitem">IP</code> address entered above.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Gateway</strong></span> — The <code class="systemitem">IP</code> address of the gateway leading to the remote network, sub-net, or host entered above.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Metric</strong></span> — A network cost, a preference value to give to this route. Lower values will be preferred over higher values.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guibutton"><strong>Automatic</strong></span> </span></dt><dd><div class="para">
+ When Automatic is <span class="guilabel"><strong>ON</strong></span>, routes from <code class="systemitem">RA</code> or <code class="systemitem">DHCP</code> are used, but you can also add additional static routes. When <span class="guilabel"><strong>OFF</strong></span>, only static routes you define are used.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Use this connection only for resources on its network</strong></span> </span></dt><dd><div class="para">
+ Select this check box to prevent the connection from becoming the default route. Typical examples are where a connection is a VPN tunnel or a leased line to a head office and you do not want any Internet-bound traffic to pass over the connection. Selecting this option means that only traffic specifically destined for routes learned automatically over the connection or entered here manually will be routed over the connection.
+ </div></dd></dl></div></div></div></div><div class="section" id="sec-Using_the_Command_Line_Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.3. Using the Command Line Interface (CLI)</h2></div></div></div><div class="section" id="sec-Configuring_a_Network_Interface_Using_ifcg_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.1. Configuring a Network Interface Using ifcfg Files</h3></div></div></div><div class="para">
+ Interface configuration files control the software interfaces for individual network devices. As the system boots, it uses these files to determine what interfaces to bring up and how to configure them. These files are usually named <code class="filename">ifcfg-<em class="replaceable"><code>name</code></em></code>, where the suffix <em class="replaceable"><code>name</code></em> refers to the name of the device that the configuration file controls. By convention, the <code class="filename">ifcfg</code> file's suffix is the same as the string given by the <code class="command">DEVICE</code> directive in the configuration file itself.
+ </div><h4 id="bh-Static_Network_Settings">Static Network Settings</h4><div class="para">
+ To configure an interface with static network settings using <code class="filename">ifcfg</code> files, for an interface with the name <span class="interface">eth0</span>, create a file with name <code class="filename">ifcfg-eth0</code> in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory as follows:
+<pre class="programlisting">DEVICE=eth0
+BOOTPROTO=none
+ONBOOT=yes
+PREFIX=24
+IPADDR=10.0.1.27
+</pre>
+ Optionally specify the hardware or MAC address using the <code class="command">HWADDR</code> directive. Note that this may influence the device naming procedure as explained in <a class="xref" href="#ch-Consistent_Network_Device_Naming">Chapter 8, <em>Consistent Network Device Naming</em></a>. You do not need to specify the network or broadcast address as this is calculated automatically by <span class="application"><strong>ipcalc</strong></span>.
+ </div><h4 id="bh-Dynamic_Network_Settings">Dynamic Network Settings</h4><div class="para">
+ To configure an interface with dynamic network settings using <code class="filename">ifcfg</code> files, for an interface with name <span class="interface">em1</span>, create a file with name <code class="filename">ifcfg-em1</code> in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory as follows:
+<pre class="programlisting">DEVICE=em1
+BOOTPROTO=dhcp
+ONBOOT=yes
+</pre>
+ Optionally specify the hardware or MAC address using the <code class="command">HWADDR</code> directive. Note that this may influence the device naming procedure as explained in <a class="xref" href="#ch-Consistent_Network_Device_Naming">Chapter 8, <em>Consistent Network Device Naming</em></a>. You do not need to specify the network or broadcast address as this is calculated automatically by <span class="application"><strong>ipcalc</strong></span>.
+ </div><div class="para">
+ To configure an interface to send a different host name to the <code class="systemitem">DHCP</code> server, add the following line to the <code class="filename">ifcfg</code> file. <pre class="synopsis">DHCP_HOSTNAME=<em class="replaceable"><code>hostname</code></em></pre>
+ </div><div class="para">
+ To configure an interface to ignore routes sent by a <code class="systemitem">DHCP</code> server, add the following line to the <code class="filename">ifcfg</code> file. <pre class="synopsis">PEERDNS=no</pre> This will prevent network service from updating <code class="filename">/etc/resolv.conf</code> with the <code class="systemitem">DNS</code> servers received from a <code class="systemitem">DHCP</code> server.
+ </div><div class="para">
+ To configure an interface to use particular <code class="systemitem">DNS</code> servers, set <code class="command">PEERDNS=no</code> as described above and add lines as follows to the <code class="filename">ifcfg</code> file:
+<pre class="programlisting">DNS1=<em class="replaceable"><code>ip-address</code></em>
+DNS2=<em class="replaceable"><code>ip-address</code></em></pre>
+ where <em class="replaceable"><code>ip-address</code></em> is the address of a <code class="systemitem">DNS</code> server. This will cause the network service to update <code class="filename">/etc/resolv.conf</code> with the <code class="systemitem">DNS</code> servers specified.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> will by default call the <code class="systemitem">DHCP</code> client, <span class="application"><strong>dhclient</strong></span>, when a profile has been set to obtain addresses automatically, or when an interface configuration file has BOOTPROTO set to <code class="literal">dhcp</code>. Where <code class="systemitem">DHCP</code> is required, an instance of <code class="systemitem">dhclient</code> is started for every Internet protocol, <code class="systemitem">IPv4</code> and <code class="systemitem">IPv6</code>, on an interface. Where <span class="application"><strong>NetworkManager</strong></span> is not running, or not managing an interface, then the legacy network service will call instances of <code class="systemitem">dhclient</code> as required.
+ </div></div><div class="section" id="sec-Configuring_a_Network_Interface_Using_ip_commands"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.2. Configuring a Network Interface Using ip Commands</h3></div></div></div><div class="para">
+ The <span class="application"><strong>ip</strong></span> utility can be used to assign <code class="systemitem">IP</code> addresses to an interface. The command takes the following form: <pre class="synopsis">ip addr [<span class="optional"> add | del </span>] <em class="replaceable"><code>address</code></em> dev <em class="replaceable"><code>ifname</code></em></pre>
+ </div><h4 id="bh-Assigning_a_Static_Address_Using_ip_Commands"> Assigning a Static Address Using ip Commands </h4><div class="para">
+ To assign an <code class="systemitem">IP</code> address to an interface, issue a command as <code class="systemitem">root</code> as follows:
+<pre class="screen">~]# <code class="command">ip address add 10.0.0.3/24 dev eth0</code>
+The address assignment of a specific device can be viewed as follows:
+~]# <code class="command">ip addr show dev eth0</code>
+2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
+ link/ether f0:de:f1:7b:6e:5f brd ff:ff:ff:ff:ff:ff
+ inet 10.0.0.3/24 brd 10.0.0.255 scope global global eth0
+ valid_lft 58682sec preferred_lft 58682sec
+ inet6 fe80::f2de:f1ff:fe7b:6e5f/64 scope link
+ valid_lft forever preferred_lft forever</pre>
+ Further examples and command options can be found in the <code class="filename">ip-address(8)</code> manual page.
+ </div><h4 id="bh-Configuring_Multiple_Addresses_Using_ip_Commands"> Configuring Multiple Addresses Using ip Commands </h4><div class="para">
+ As the <span class="application"><strong>ip</strong></span> utility supports assigning multiple addresses to the same interface it is no longer necessary to use the alias interface method of binding multiple addresses to the same interface. The <span class="application"><strong>ip</strong></span> command to assign an address can be repeated multiple times in order to assign multiple address. For example:
+<pre class="screen">~]# <code class="command">ip address add 192.168.2.223/24 dev eth1</code>
+~]# <code class="command">ip address add 192.168.4.223/24 dev eth1</code>
+~]# <code class="command">ip addr</code>
+3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
+ link/ether 52:54:00:fb:77:9e brd ff:ff:ff:ff:ff:ff
+ inet 192.168.<span class="bold bold"><strong>2</strong></span>.223/24 scope global eth1
+ inet 192.168.<span class="bold bold"><strong>4</strong></span>.223/24 scope global eth1</pre>
+
+ </div><div class="para">
+ The commands for the <span class="application"><strong>ip</strong></span> utility are documented in the <code class="filename">ip(8)</code> manual page.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that <span class="application"><strong>ip</strong></span> commands given on the command line will not persist after a system restart.
+ </div></div></div></div><div class="section" id="sec-Static-Routes_and_the_Default_Gateway"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.3. Static Routes and the Default Gateway</h3></div></div></div><div class="para">
+ Static routes are for traffic that must not, or should not, go through the default gateway. Routing is often handled by devices on the network dedicated to routing (although any device can be configured to perform routing). Therefore, it is often not necessary to configure static routes on Fedora servers or clients. Exceptions include traffic that must pass through an encrypted VPN tunnel or traffic that should take a specific route for reasons of cost or security. The default gateway is for any and all traffic which is not destined for the local network and for which no preferred route is specified in the routing table. The default gateway is traditionally a dedicated network router.
+ </div><h4 id="bh-networkscripts-static-routes"> Configuring Static Routes Using the Command Line </h4><a id="idm225454056704" class="indexterm"></a><div class="para">
+ If static routes are required, they can be added to the routing table by means of the <code class="command">ip route add</code> command and removed using the <code class="command">ip route del</code> command. The more frequently used <code class="command">ip route</code> commands take the following form: <pre class="synopsis">ip route [<span class="optional"> add | del | change | append | replace </span>] <em class="replaceable"><code>destination-address</code></em></pre> See the <code class="filename">ip-route(8)</code> man page for more details on the options and formats.
+ </div><div class="para">
+ Use the <code class="command">ip route</code> command without options to display the <code class="systemitem">IP</code> routing table. For example:
+<pre class="screen">~]$ ip route
+default via 192.168.122.1 dev eth1 proto static metric 1024
+192.168.122.0/24 dev eth1 proto kernel scope link src 192.168.122.107
+192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.126</pre>
+ </div><div class="para">
+ To add a static route to a host address, in other words to a single <code class="systemitem">IP</code> address, issue a command as <code class="systemitem">root</code>:
+<pre class="screen">ip route add <em class="replaceable"><code>192.0.2.1</code></em> via <em class="replaceable"><code>10.0.0.1</code></em> [<span class="optional"><code class="option">dev</code> <em class="replaceable"><code>ifname</code></em></span>]</pre>
+ Where <em class="replaceable"><code>192.0.2.1</code></em> is the <code class="systemitem">IP</code> address of the host in dotted decimal notation, <em class="replaceable"><code>10.0.0.1</code></em> is the next hop address and <em class="replaceable"><code>ifname</code></em> is the exit interface leading to the next hop.
+ </div><div class="para">
+ To add a static route to a network, in other words to an <code class="systemitem">IP</code> address representing a range of <code class="systemitem">IP</code> addresses, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">ip route add <em class="replaceable"><code>192.0.2.0/24</code></em> via <em class="replaceable"><code>10.0.0.1</code></em> [<span class="optional"><code class="option">dev</code> <em class="replaceable"><code>ifname</code></em></span>]</pre>
+ where <em class="replaceable"><code>192.0.2.0</code></em> is the <code class="systemitem">IP</code> address of the destination network in dotted decimal notation and <em class="replaceable"><code>/24</code></em> is the network prefix. The network prefix is the number of enabled bits in the subnet mask. This format of network address slash network prefix length is sometimes referred to as <em class="firstterm">classless inter-domain routing</em> (<acronym class="acronym">CIDR</acronym>) notation.
+ </div><div class="para">
+ Static route configuration can be stored per-interface in a <code class="filename">/etc/sysconfig/network-scripts/route-<em class="replaceable"><code>interface</code></em></code> file. For example, static routes for the <span class="interface">eth0</span> interface would be stored in the <code class="filename">/etc/sysconfig/network-scripts/route-eth0</code> file. The <code class="filename">route-<em class="replaceable"><code>interface</code></em></code> file has two formats: <span class="application"><strong>ip</strong></span> command arguments and network/netmask directives. These are described below.
+ </div><div class="para">
+ See the <code class="filename">ip-route(8)</code> man page for more information on the <code class="command">ip route</code> command.
+ </div><h4 id="bh-networkscripts-default-gateway"> Configuring The Default Gateway </h4><a id="idm225462510464" class="indexterm"></a><div class="para">
+ The default gateway is determined by the network scripts which parse the <code class="filename">/etc/sysconfig/network</code> file first and then the network interface <code class="literal">ifcfg</code> files for interfaces that are <span class="quote">“<span class="quote">up</span>”</span>. The <code class="literal">ifcfg</code> files are parsed in numerically ascending order, and the last GATEWAY directive to be read is used to compose a default route in the routing table.
+ </div><div class="para">
+ The default route can thus be indicated by means of the GATEWAY directive and can be specified either globally or in interface-specific configuration files. Specifying the gateway globally has certain advantages in static networking environments, especially if more than one network interface is present. It can make fault finding simpler if applied consistently.
+ </div><div class="para">
+ In dynamic network environments, where mobile hosts are managed by <span class="application"><strong>NetworkManager</strong></span>, gateway information is likely to be interface specific and is best left to be assigned by <code class="systemitem">DHCP</code>. In special cases where it is necessary to influence <span class="application"><strong>NetworkManager</strong></span>'s selection of the exit interface to be used to reach a gateway, make use of the <code class="command">DEFROUTE=no</code> command in the <code class="literal">ifcfg</code> files for those interfaces which do not lead to the default gateway.
+ </div><div class="para">
+ Global default gateway configuration is stored in the <code class="filename">/etc/sysconfig/network</code> file. This file specifies gateway and host information for all network interfaces.
+ </div></div><div class="section" id="sec-Configuring_Static_Routes_in_ifcfg_files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.4. Configuring Static Routes in ifcfg files</h3></div></div></div><div class="para">
+ Static routes set using <span class="application"><strong>ip</strong></span> commands on the command line will be lost if the system is shutdown or restarted. To configure static routes to be persistent after a system restart, they must be placed in per-interface configuration files in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory. The file name should be of the format <code class="filename">route-<em class="replaceable"><code>ifname</code></em></code>. There are two types of commands to use in the configuration files; <span class="application"><strong>ip</strong></span> commands as explained in <a class="xref" href="#sec-networkscripts-static-routes-ip-command">Section 2.3.4.1, “Static Routes Using the IP Command Arguments Format”</a> and the <em class="firstterm">Network/Netmask</em> format as explained in <a class="xref" href="#sec-networkscripts-static-routes-network-netmask-directives">Section 2.3.4.2, “Network/Netmask Directive
s Format”</a>.
+ </div><div class="section" id="sec-networkscripts-static-routes-ip-command"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.4.1. Static Routes Using the IP Command Arguments Format</h4></div></div></div><div class="para">
+ If required in a per-interface configuration file, for example <code class="filename">/etc/sysconfig/network-scripts/route-eth0</code>, define a route to a default gateway on the first line. This is only required if the gateway is not set via <code class="systemitem">DHCP</code> and is not set globally in the <code class="filename">/etc/sysconfig/network</code> file:
+ </div><pre class="synopsis">default via <em class="replaceable"><code>192.168.1.1</code></em> <code class="option">dev</code> <em class="replaceable"><code>interface</code></em></pre><div class="para">
+ where <em class="replaceable"><code>192.168.1.1</code></em> is the <code class="systemitem">IP</code> address of the default gateway. The <em class="replaceable"><code>interface</code></em> is the interface that is connected to, or can reach, the default gateway. The <code class="option">dev</code> option can be omitted, it is optional. Note that this setting takes precedence over a setting in the <code class="filename">/etc/sysconfig/network</code> file.
+ </div><div class="para">
+ If a route to a remote network is required, a static route can be specified as follows. Each line is parsed as an individual route:
+ </div><pre class="synopsis"><em class="replaceable"><code>10.10.10.0/24</code></em> via <em class="replaceable"><code>192.168.1.1</code></em> [<span class="optional"><code class="option">dev</code> <em class="replaceable"><code>interface</code></em></span>]</pre><div class="para">
+ where <em class="replaceable"><code>10.10.10.0/24</code></em> is the network address and prefix length of the remote or destination network. The address <em class="replaceable"><code>192.168.1.1</code></em> is the <code class="systemitem">IP</code> address leading to the remote network. It is preferably the <em class="firstterm">next hop address</em> but the address of the exit interface will work. The <span class="quote">“<span class="quote">next hop</span>”</span> means the remote end of a link, for example a gateway or router. The <code class="option">dev</code> option can be used to specify the exit interface <em class="replaceable"><code>interface</code></em> but it is not required. Add as many static routes as required.
+ </div><div class="para">
+ The following is an example of a <code class="filename">route-<em class="replaceable"><code>interface</code></em></code> file using the <span class="application"><strong>ip</strong></span> command arguments format. The default gateway is <code class="systemitem">192.168.0.1</code>, interface <span class="interface">eth0</span> and a leased line or WAN connection is available at <code class="systemitem">192.168.0.10</code>. The two static routes are for reaching the <code class="systemitem">10.10.10.0/24</code> network and the <code class="systemitem">172.16.1.10/32</code> host:
+ </div><pre class="screen">default via 192.168.0.1 dev eth0
+10.10.10.0/24 via 192.168.0.10 dev eth0
+172.16.1.10/32 via 192.168.0.10 dev eth0</pre><div class="para">
+ In the above example, packets going to the local <code class="systemitem">192.168.0.0/24</code> network will be directed out the interface attached to that network. Packets going to the <code class="systemitem">10.10.10.0/24</code> network and <code class="systemitem">172.16.1.10/32</code> host will be directed to <code class="systemitem">192.168.0.10</code>. Packets to unknown, remote, networks will use the default gateway therefore static routes should only be configured for remote networks or hosts if the default route is not suitable. Remote in this context means any networks or hosts that are not directly attached to the system.
+ </div><div class="para">
+ Specifying an exit interface is optional. It can be useful if you want to force traffic out of a specific interface. For example, in the case of a VPN, you can force traffic to a remote network to pass through a <span class="interface">tun0</span> interface even when the interface is in a different subnet to the destination network.
+ </div><div class="important"><div class="admonition_header"><h2>Duplicate default gateways</h2></div><div class="admonition"><div class="para">
+ If the default gateway is already assigned by <code class="systemitem">DHCP</code> and if the same gateway with the same metric is specified in a configuration file, an error during start-up, or when bringing up an interface, will occur. The follow error message may be shown: "RTNETLINK answers: File exists". This error may be ignored.
+ </div></div></div></div><div class="section" id="sec-networkscripts-static-routes-network-netmask-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.4.2. Network/Netmask Directives Format</h4></div></div></div><div class="para">
+ You can also use the network/netmask directives format for <code class="filename">route-<em class="replaceable"><code>interface</code></em></code> files. The following is a template for the network/netmask format, with instructions following afterwards:
+ </div><pre class="synopsis"> ADDRESS0=<em class="replaceable"><code>10.10.10.0</code></em> NETMASK0=<em class="replaceable"><code>255.255.255.0</code></em> GATEWAY0=<em class="replaceable"><code>192.168.1.1</code></em> </pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>10.10.10.0</code></em></code> is the network address of the remote network or host to be reached.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">NETMASK0=<em class="replaceable"><code>255.255.255.0</code></em></code> is the netmask for the network address defined with <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>10.10.10.0</code></em></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">GATEWAY0=<em class="replaceable"><code>192.168.1.1</code></em></code> is the default gateway, or an <code class="systemitem">IP</code> address that can be used to reach <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>10.10.10.0</code></em></code>
+ </div></li></ul></div><div class="para">
+ The following is an example of a <code class="filename">route-<em class="replaceable"><code>interface</code></em></code> file using the network/netmask directives format. The default gateway is <code class="systemitem">192.168.0.1</code> but a leased line or WAN connection is available at <code class="systemitem">192.168.0.10</code>. The two static routes are for reaching the <code class="systemitem">10.10.10.0/24</code> and <code class="systemitem">172.16.1.0/24</code> networks:
+ </div><pre class="programlisting">ADDRESS0=10.10.10.0
+NETMASK0=255.255.255.0
+GATEWAY0=192.168.0.10
+ADDRESS1=172.16.1.10
+NETMASK1=255.255.255.0
+GATEWAY1=192.168.0.10</pre><div class="para">
+ Subsequent static routes must be numbered sequentially, and must not skip any values. For example, <code class="computeroutput">ADDRESS0</code>, <code class="computeroutput">ADDRESS1</code>, <code class="computeroutput">ADDRESS2</code>, and so on.
+ </div></div></div><div class="section" id="sec-Configuring_IPv6_Tokenized_Interface_Identifiers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.5. Configuring IPv6 Tokenized Interface Identifiers</h3></div></div></div><div class="para">
+ In a network, servers are generally given static addresses and these are usually configured manually to avoid relying on a <code class="systemitem">DHCP</code> server which may fail or run out of addresses. The <code class="systemitem">IPv6</code> protocol introduced <em class="firstterm">Stateless Address Autoconfiguration</em> (<acronym class="acronym">SLAAC</acronym>) which enables clients to assign themselves an address without relying on a <code class="systemitem">DHCPv6</code> server. SLAAC derives the <code class="systemitem">IPv6</code> address based on the interface hardware, therefore it should not be used for servers in case the hardware is changed and the associated SLAAC generated address changes with it. In an <code class="systemitem">IPv6</code> environment, if the network prefix is changed, or the system is moved to a new location, any manually configured static addresses would have to be edited due to the changed prefix.
+ </div><div class="para">
+ To address these problems, the IETF draft <a href="https://tools.ietf.org/id/draft-chown-6man-tokenised-ipv6-identifiers-02.txt"><em class="citetitle">Tokenised IPv6 Identifiers</em></a> has been implemented in the kernel together with corresponding additions to the <code class="command">ip</code> utility. This enables the lower 64 bit interface identifier part of the <code class="systemitem">IPv6</code> address to be based on a token, supplied by the administrator, leaving the network prefix, the higher 64 bits, to be obtained from <em class="firstterm">router advertisements</em> (<acronym class="acronym">RA</acronym>). This means that if the network interface hardware is changed, the lower 64 bits of the address will not change, and if the system is moved to another network, the network prefix will be obtained from router advertisements automatically, thus no manual editing is required.
+ </div><div class="para">
+ To configure an interface to use a tokenized <code class="systemitem">IPv6</code> identifier, issue a command in the following format as <code class="systemitem">root</code> user:
+<pre class="screen">~]# <code class="command">ip token set ::1a:2b:3c:4d/64 dev eth4</code></pre>
+ Where <code class="literal">::1a:2b:3c:4d/64</code> is the token to be used. This setting is not persistent. To make it persistent, add the command to an init script. See <a class="xref" href="#sec-Network_Configuration_Using_sysconfig_Files">Section 1.7, “Network Configuration Using sysconfig Files”</a> for information on network scripts.
+ </div><div class="para">
+ Using a memorable token is possible, but is limited to the range of valid hexadecimal digits. For example, for a <code class="systemitem">DNS</code> server, which traditionally uses port <code class="literal">53</code>, a token of <code class="literal">::53/64</code> could be used.
+ </div><div class="para">
+ To view all the configured <code class="systemitem">IPv6</code> tokens, issue the following command:
+<pre class="screen">~]$ <code class="command">ip token</code>
+ token :: dev eth0
+ token :: dev eth1
+ token :: dev eth2
+ token :: dev eth3
+ token ::1a:2b:3c:4d dev eth4</pre>
+
+ </div><div class="para">
+ To view the configured <code class="systemitem">IPv6</code> token for a specific interface, issue the following command:
+<pre class="screen">~]$ <code class="command">ip token get dev eth4</code>
+ token ::1a:2b:3c:4d dev eth4</pre>
+
+ </div><div class="para">
+ Note that adding a token to an interface will replace a previously allocated token, and in turn invalidate the address derived from it. Supplying a new token causes a new address to be generated and applied, but this process will leave any other addresses unchanged. In other words, a new tokenized identifier only replaces a previously existing tokenized identifier, not any other <code class="systemitem">IP</code> address.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Take care not to add the same token to more than one system or interface. The duplicate address detection (<acronym class="acronym">DAD</acronym>) mechanism will remove the duplicate address from the interface but it cannot change the configuration. Once a token is set, it cannot be cleared or reset, except by rebooting the machine.
+ </div></div></div></div></div><div class="section" id="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.4. Using the NetworkManager Command Line Tool, nmcli</h2></div></div></div><div class="para">
+ The command‐line tool <span class="application"><strong>nmcli</strong></span> can be used by both users and scripts for controlling <span class="application"><strong>NetworkManager</strong></span>. The basic format of a command is as follows: <pre class="synopsis">nmcli <code class="option">OPTIONS</code> OBJECT { <code class="command">COMMAND</code> | help }</pre> where OBJECT can be one of <code class="literal">general</code>, <code class="literal">networking</code>, <code class="literal">radio</code>, <code class="literal">connection</code>, or <code class="literal">device</code>. The most used options are: <code class="option">-t, --terse</code> for use in scripts, the <code class="option">-p, --pretty</code> option for users, and the <code class="option">-h, --help</code> option. Command completion has been implemented for <span class="application"><strong>nmcli</strong></span>, so remember to press <span class="keycap"><strong>Tab</strong></span> whenever you are
unsure of the command options available. See the <code class="filename">nmcli(1)</code> man page for a complete list of the options and commands.
+ </div><div class="para">
+ The <span class="application"><strong>nmcli</strong></span> tool has some built-in context-sensitive help. For example, issue the following two commands and notice the difference:
+<pre class="screen">~]$ <code class="command">nmcli help</code>
+Usage: nmcli [OPTIONS] OBJECT { COMMAND | help }
+
+OPTIONS
+ -t[erse] terse output
+ -p[retty] pretty output
+ -m[ode] tabular|multiline output mode
+ -f[ields] <field1,field2,...>|all|common specify fields to output
+ -e[scape] yes|no escape columns separators in values
+ -n[ocheck] don't check nmcli and NetworkManager versions
+ -a[sk] ask for missing parameters
+ -w[ait] <seconds> set timeout waiting for finishing operations
+ -v[ersion] show program version
+ -h[elp] print this help
+
+OBJECT
+ g[eneral] NetworkManager's general status and operations
+ n[etworking] overall networking control
+ r[adio] NetworkManager radio switches
+ c[onnection] NetworkManager's connections
+ d[evice] devices managed by NetworkManager</pre>
+
+<pre class="screen">~]$ <code class="command">nmcli general help</code>
+Usage: nmcli general { COMMAND | help }
+
+ COMMAND := { status | hostname | permissions | logging }
+
+ status
+
+ hostname [<hostname>]
+
+ permissions
+
+ logging [level <log level>] [domains <log domains>]</pre>
+ In the second example above the help is related to the object <code class="literal">general</code>.
+ </div><div class="para">
+ The <code class="filename">nmcli-examples(5)</code> man page has many useful examples. A brief selection is shown here:
+ </div><div class="para">
+ To show the overall status of <span class="application"><strong>NetworkManager</strong></span>: <pre class="synopsis">nmcli general status</pre> To control <span class="application"><strong>NetworkManager</strong></span> logging: <pre class="synopsis">nmcli general logging</pre> To show all connections: <pre class="synopsis">nmcli connection show</pre> To show only currently active connections, add the <code class="option">-a, --active</code> option as follows: <pre class="synopsis">nmcli connection show --active</pre> To show devices recognized by <span class="application"><strong>NetworkManager</strong></span> and their state: <pre class="synopsis">nmcli device status</pre>
+ </div><div class="para">
+ Commands can be shortened and some options omitted. For example the command: <pre class="synopsis">nmcli connection modify id '<em class="replaceable"><code>MyCafe</code></em>' 802-11-wireless.mtu 1350</pre> Can be reduced to the following command: <pre class="synopsis">nmcli con mod <em class="replaceable"><code>MyCafe</code></em> 802-11-wireless.mtu 1350</pre> The <code class="option">id</code> option can been omitted because the connection ID (name) is unambiguous for <span class="application"><strong>nmcli</strong></span> in this case. As you become familiar with the commands, further abbreviations can be made. For example: <pre class="synopsis">nmcli connection add type ethernet</pre> can be reduced to: <pre class="synopsis">nmcli c a type eth</pre> <div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Remember to use tab completion when in doubt.
+ </div></div></div>
+ </div><h3 id="bh-Starting_and_Stopping_an_Interface_Using_nmcli">Starting and Stopping an Interface Using nmcli</h3><div class="para">
+ The <span class="application"><strong>nmcli</strong></span> tool can be used to start and stop any network interface, including masters. For example:
+<pre class="screen">nmcli con up id bond0
+nmcli con up id port0
+nmcli dev disconnect iface bond0
+nmcli dev disconnect iface eth0</pre>
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ It is recommended to use <code class="command">nmcli dev disconnect iface <em class="replaceable"><code>iface-name</code></em></code> rather than <code class="command">nmcli con down id <em class="replaceable"><code>id-string</code></em></code> because disconnection places the interface into a <span class="quote">“<span class="quote">manual</span>”</span> mode, in which no automatic connection will be started until the user tells <span class="application"><strong>NetworkManager</strong></span> to start a connection or until an external event like a carrier change, hibernate, or sleep, occurs.
+ </div></div></div><h3 id="bh-The_nmcli_Interactive_Connection_Editor">The nmcli Interactive Connection Editor</h3><div class="para">
+ The <span class="application"><strong>nmcli</strong></span> tool has an interactive connection editor. To use it, enter the following command:
+<pre class="screen">~]$ <code class="command">nmcli con edit</code></pre>
+ You will be prompted to enter a valid connection type from the list displayed. After entering a connection type you will be placed at the <span class="application"><strong>nmcli</strong></span> prompt. If you are familiar with the connection types you can add a valid connection <code class="option">type</code> option to the <code class="command">nmcli con edit</code> command and be taken straight to the <span class="application"><strong>nmcli</strong></span> prompt. The format is as follows for editing an existing connection profile: <pre class="synopsis">nmcli con edit [id | uuid | path] <em class="replaceable"><code>ID</code></em></pre> For adding and editing a new connection profile, the following format applies: <pre class="synopsis">nmcli con edit [type <em class="replaceable"><code>new-connection-type</code></em>] [con-name <em class="replaceable"><code>new-connection-name</code></em>]</pre>
+ </div><div class="para">
+ Type <code class="command">help</code> at the <span class="application"><strong>nmcli</strong></span> prompt to see a list of valid commands. Use the <code class="command">describe</code> command to get a description of settings and their properties. The format is as follows: <pre class="synopsis">describe <em class="replaceable"><code>setting.property</code></em></pre> For example:
+<pre class="screen">nmcli> <code class="command">describe team.config</code></pre>
+
+ </div><div class="section" id="sec-Understanding_the_nmcli_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.1. Understanding the nmcli Options</h3></div></div></div><div class="para">
+ Many of the <span class="application"><strong>nmcli</strong></span> commands are self-explanatory, however a few command options are worth a moments study:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">type</code> — The connection type.</span></dt><dd><div class="para">
+ Allowed values are: <code class="literal">adsl</code>, <code class="literal">bond</code>, <code class="literal">bond-slave</code>, <code class="literal">bridge</code>, <code class="literal">bridge-slave</code>, <code class="literal">bluetooth</code>, <code class="literal">cdma</code>, <code class="literal">ethernet</code>, <code class="literal">gsm</code>, <code class="literal">infiniband</code>, <code class="literal">olpc-mesh</code>, <code class="literal">team</code>, <code class="literal">team-slave</code>, <code class="literal">vlan</code>, <code class="literal">wifi</code>, <code class="literal">wimax</code>.
+ </div><div class="para">
+ Each connection type has type-specific command options. Press <span class="keycap"><strong>Tab</strong></span> to see a list of them or see the <code class="literal">TYPE_SPECIFIC_OPTIONS</code> list in the <code class="filename">nmcli(1)</code> man page. The <code class="option">type</code> option is applicable after the following: <code class="command">nmcli connection add</code> and <code class="command">nmcli connection edit</code>.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">con-name</code> — The name assigned to a connection profile.</span></dt><dd><div class="para">
+ If you do not specify a connection name, one will be generated as follows: <pre class="synopsis"> <code class="literal">type</code>-ifname[-number]</pre>
+ </div><div class="para">
+ The connection name is the name of a <em class="firstterm">connection profile</em> and should not be confused with the interface name that denotes a device (<span class="interface">wlan0</span>, <span class="interface">eth0</span>, <span class="interface">em1</span>, and so on). Users can however name the connections after interfaces, but they are not the same thing. There can be multiple connection profiles available for a device. This is particularly useful for mobile devices or when switching a network cable back and forth between different devices. Rather than edit the configuration, create different profiles and apply them to the interface as needed. The <code class="option">id</code> option also refers to the connection profile name.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">id</code> — An identification string assigned by the user to a connection profile.</span></dt><dd><div class="para">
+ The ID can be used in <code class="command">nmcli connection</code> commands to identify a connection. The NAME field in the output always denotes the connection ID (name). It refers to the same connection profile name that the <code class="command">con-name</code> does.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">uuid</code> — A unique identification string assigned by the system to a connection profile.</span></dt><dd><div class="para">
+ The UUID can be used in <code class="command">nmcli connection</code> commands to identify a connection.
+ </div></dd></dl></div></div><div class="section" id="sec-Connecting_to_a_Network_Using_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.2. Connecting to a Network Using nmcli</h3></div></div></div><div class="para">
+ To list the currently available network connections, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con show</code>
+NAME UUID TYPE DEVICE
+eth0 96a5deb0-5eb0-41e1-a7ed-38fea413f9c8 802-3-ethernet eth0
+MyWiFi 91451385-4eb8-4080-8b82 802-11-wireless wlan0</pre>
+ Note that the NAME field in the output always denotes the connection ID (name). It is not the interface name even though it might look the same. In the example above <code class="literal">eth0</code> is the connection ID given by the user to the profile applied to the interface <span class="interface">eth0</span>. In the second line the user has assigned the connection ID <code class="literal">MyWiFi</code> to the interface <code class="literal">wlan0</code>.
+ </div><div class="para">
+ Adding an Ethernet connection means creating a configuration profile which is then assigned to a device. Before creating a new profile, review the available devices as follows:
+<pre class="screen">~]$ <code class="command">nmcli dev status</code>
+DEVICE TYPE STATE CONNECTION
+wlan0 wifi connected my-ssid
+eth0 ethernet unavailable --
+lo loopback unmanaged --</pre>
+
+ </div><h4 id="Adding_a_Dynamic_Ethernet_Connection">Adding a Dynamic Ethernet Connection</h4><div class="para">
+ To add an Ethernet configuration profile with dynamic <code class="systemitem">IP</code> configuration, allowing <code class="systemitem">DHCP</code> to assign the network configuration, a command in the following format can be used: <pre class="synopsis">nmcli connection add type ethernet con-name <em class="replaceable"><code>connection-name</code></em> ifname <em class="replaceable"><code>interface-name</code></em></pre>
+ </div><div class="para">
+ For example, to create a dynamic connection profile named <em class="replaceable"><code>my-office</code></em>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type ethernet con-name <em class="replaceable"><code>my-office</code></em> ifname <em class="replaceable"><code>eth0</code></em></code>
+Connection 'my-office' (0a053110-5361-412c-a4fb-6ff20877e9e4) successfully added.</pre>
+ <span class="application"><strong>NetworkManager</strong></span> will set its internal parameter <code class="option">connection.autoconnect</code> to <code class="literal">yes</code>. <span class="application"><strong>NetworkManager</strong></span> will also write out settings to <code class="filename">/etc/sysconfig/network-scripts/ifcfg-my-office</code> where the ONBOOT directive will be set to <code class="literal">yes</code>.
+ </div><div class="para">
+ Note that manual changes to the ifcfg file will not be noticed by <span class="application"><strong>NetworkManager</strong></span> until the interface is next brought up. See <a class="xref" href="#sec-Network_Configuration_Using_sysconfig_Files">Section 1.7, “Network Configuration Using sysconfig Files”</a> for more information on using configuration files.
+ </div><div class="para">
+ To bring up the Ethernet connection, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con up <em class="replaceable"><code>my-office</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/1)</pre>
+ Review the status of the devices and connections:
+<pre class="screen">~]$ <code class="command">nmcli device status</code>
+DEVICE TYPE STATE CONNECTION
+eth0 ethernet connected my-office
+lo loopback unmanaged --</pre>
+
+ </div><div class="para">
+ To change the host name sent by a host to a <code class="systemitem">DHCP</code> server, modify the <code class="option">dhcp-hostname</code> property as follows:
+<pre class="screen">~]$ <code class="command">nmcli con modify my-office <em class="replaceable"><code>my-office</code></em> ipv4.dhcp-hostname <em class="replaceable"><code>host-name</code></em> ipv6.dhcp-hostname <em class="replaceable"><code>host-name</code></em></code></pre>
+ </div><div class="para">
+ To change the <code class="systemitem">IPv4</code> client ID sent by a host to a <code class="systemitem">DHCP</code> server, modify the <code class="option">dhcp-client-id</code> property as follows:
+<pre class="screen">~]$ <code class="command">nmcli con modify my-office <em class="replaceable"><code>my-office</code></em> ipv4.dhcp-client-id <em class="replaceable"><code>client-ID-string</code></em></code></pre>
+ There is no <code class="option">dhcp-client-id</code> property for <code class="systemitem">IPv6</code>, <span class="application"><strong>dhclient</strong></span> creates an identifier for <code class="systemitem">IPv6</code>. See the <code class="filename">dhclient(8)</code> man page for details.
+ </div><div class="para">
+ To ignore the <code class="systemitem">DNS</code> servers sent to a host by a <code class="systemitem">DHCP</code> server, modify the <code class="option">ignore-auto-dns</code> property as follows:
+<pre class="screen">~]$ <code class="command">nmcli con modify my-office <em class="replaceable"><code>my-office</code></em> ipv4.ignore-auto-dns <em class="replaceable"><code>yes</code></em> ipv6.ignore-auto-dns <em class="replaceable"><code>yes</code></em></code></pre>
+ </div><div class="para">
+ See the <code class="filename">nm-settings(5)</code> man page for more information on properties and their settings.
+ </div><div class="example" id="ex-Configuring_a_Dynamic_Ethernet_Connection_Using_the_Interactive_Editor"><h6>Example 2.1. Configuring a Dynamic Ethernet Connection Using the Interactive Editor</h6><div class="example-contents"><div class="para">
+ To configure a dynamic Ethernet connection using the interactive editor, issue commands as follows:
+<pre class="screen">~]$ <code class="command">nmcli con edit type ethernet con-name <em class="replaceable"><code>eth0</code></em></code>
+
+===| nmcli interactive connection editor |===
+
+Adding a new '802-3-ethernet' connection
+
+Type 'help' or '?' for available commands.
+Type 'describe [<setting>.<prop>]' for detailed property description.
+
+You may edit the following settings: connection, 802-3-ethernet (ethernet), 802-1x, ipv4, ipv6, dcb
+nmcli> describe ipv4.method
+
+=== [method] ===
+[NM property description]
+IPv4 configuration method. If 'auto' is specified then the appropriate automatic method (DHCP, PPP, etc) is used for the interface and most other properties can be left unset. If 'link-local' is specified, then a link-local address in the 169.254/16 range will be assigned to the interface. If 'manual' is specified, static IP addressing is used and at least one IP address must be given in the 'addresses' property. If 'shared' is specified (indicating that this connection will provide network access to other computers) then the interface is assigned an address in the 10.42.x.1/24 range and a DHCP and forwarding DNS server are started, and the interface is NAT-ed to the current default network connection. 'disabled' means IPv4 will not be used on this connection. This property must be set.
+
+nmcli> set ipv4.method auto
+nmcli> save
+Saving the connection with 'autoconnect=yes'. That might result in an immediate activation of the connection.
+Do you still want to save? [yes] yes
+Connection 'eth0' (090b61f7-540f-4dd6-bf1f-a905831fc287) successfully saved.
+nmcli> quit
+~]$</pre>
+ The default action is to save the connection profile as persistent. If required, the profile can be held in memory only, until the next restart, by means of the <code class="command">save temporary</code> command.
+ </div></div></div><br class="example-break" /><h4 id="Adding_a_Static_Ethernet_Connection">Adding a Static Ethernet Connection</h4><div class="para">
+ To add an Ethernet connection with static <code class="systemitem">IPv4</code> configuration, a command in the following format can be used: <pre class="synopsis">nmcli connection add type ethernet con-name <em class="replaceable"><code>connection-name</code></em> ifname <em class="replaceable"><code>interface-name</code></em> ip4 <em class="replaceable"><code>address</code></em> gw4 <em class="replaceable"><code>address</code></em></pre> <code class="systemitem">IPv6</code> address and gateway information can be added using the <code class="option">ip6</code> and <code class="option">gw6</code> options.
+ </div><div class="para">
+ For example, a command to create a static Ethernet connection with only <code class="systemitem">IPv4</code> address and gateway is as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type ethernet con-name <em class="replaceable"><code>test-lab</code></em> ifname <em class="replaceable"><code>eth1</code></em> ip4 10.10.10.10/24 \</code>
+<code class="command">gw4 10.10.10.254</code></pre>
+ Optionally, at the same time specify <code class="systemitem">IPv6</code> address and gateway for the device as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type ethernet con-name <em class="replaceable"><code>test-lab</code></em> ifname <em class="replaceable"><code>eth1</code></em> ip4 10.10.10.10/24 \</code>
+<code class="command">gw4 10.10.10.254 ip6 abbe::cafe gw6 2001:db8::1</code>
+Connection 'test-lab' (05abfd5e-324e-4461-844e-8501ba704773) successfully added.</pre>
+ <span class="application"><strong>NetworkManager</strong></span> will set its internal parameter <code class="option">ipv4.method</code> to <code class="literal">manual</code> and <code class="option">connection.autoconnect</code> to <code class="literal">yes</code>. <span class="application"><strong>NetworkManager</strong></span> will also write out settings to <code class="filename">/etc/sysconfig/network-scripts/ifcfg-my-office</code> where the corresponding BOOTPROTO will be set to <code class="literal">none</code> and ONBOOT will be set to <code class="literal">yes</code>.
+ </div><div class="para">
+ Note that manual changes to the ifcfg file will not be noticed by <span class="application"><strong>NetworkManger</strong></span> until the interface is next brought up. See <a class="xref" href="#sec-Network_Configuration_Using_sysconfig_Files">Section 1.7, “Network Configuration Using sysconfig Files”</a> for more information on using configuration files.
+ </div><div class="para">
+ To set two <code class="systemitem">IPv4</code> <code class="systemitem">DNS</code> server addresses:
+<pre class="screen">~]$ <code class="command">nmcli con mod <em class="replaceable"><code>test-lab</code></em> ipv4.dns "8.8.8.8 8.8.4.4"</code></pre>
+ Note that this will replace any previously set <code class="systemitem">DNS</code> servers. To set two <code class="systemitem">IPv6</code> <code class="systemitem">DNS</code> server addresses:
+<pre class="screen">~]$ <code class="command">nmcli con mod <em class="replaceable"><code>test-lab</code></em> ipv6.dns "2001:4860:4860::8888 2001:4860:4860::8844"</code></pre>
+ Note that this will replace any previously set <code class="systemitem">DNS</code> servers. Alternatively, to add additional <code class="systemitem">DNS</code> servers to any previously set, use the <code class="literal">+</code> prefix as follows:
+<pre class="screen">~]$ <code class="command">nmcli con mod <em class="replaceable"><code>test-lab</code></em> +ipv4.dns "8.8.8.8 8.8.4.4"</code></pre>
+
+<pre class="screen">~]$ <code class="command">nmcli con mod <em class="replaceable"><code>test-lab</code></em> +ipv6.dns "2001:4860:4860::8888 2001:4860:4860::8844"</code></pre>
+ </div><div class="para">
+ To bring up the new Ethernet connection, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con up <em class="replaceable"><code>test-lab</code></em> ifname <em class="replaceable"><code>eth1</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/2</pre>
+ Review the status of the devices and connections:
+<pre class="screen">~]$ <code class="command">nmcli device status</code>
+DEVICE TYPE STATE CONNECTION
+eth0 ethernet connected my-office
+eth1 ethernet connected test-lab
+lo loopback unmanaged --</pre>
+ </div><div class="para">
+ To view detailed information about the newly configured connection, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli -p con show <em class="replaceable"><code>test-lab</code></em></code>
+===============================================================================
+ Connection profile details (test-lab)
+===============================================================================
+connection.id: test-lab
+connection.uuid: 05abfd5e-324e-4461-844e-8501ba704773
+connection.interface-name: eth1
+connection.type: 802-3-ethernet
+connection.autoconnect: yes
+connection.timestamp: 1410428968
+connection.read-only: no
+connection.permissions:
+connection.zone: --
+connection.master: --
+connection.slave-type: --
+connection.secondaries:
+connection.gateway-ping-timeout: 0
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em></pre>
+ The use of the <code class="option">-p, --pretty</code> option adds a title banner and section breaks to the output.
+ </div><div class="example" id="ex-Configuring_a_Static_Ethernet_Connection_Using_the_Interactive_Editor"><h6>Example 2.2. Configuring a Static Ethernet Connection Using the Interactive Editor</h6><div class="example-contents"><div class="para">
+ To configure a static Ethernet connection using the interactive editor, issue commands as follows:
+<pre class="screen">~]$ <code class="command">nmcli con edit type ethernet con-name <em class="replaceable"><code>eth0</code></em></code>
+
+===| nmcli interactive connection editor |===
+
+Adding a new '802-3-ethernet' connection
+
+Type 'help' or '?' for available commands.
+Type 'describe [>setting<.>prop<]' for detailed property description.
+
+You may edit the following settings: connection, 802-3-ethernet (ethernet), 802-1x, ipv4, ipv6, dcb
+nmcli> set ipv4.addresses 192.168.122.88/24
+Do you also want to set 'ipv4.method' to 'manual'? [yes]: yes
+nmcli>
+nmcli> save temporary
+Saving the connection with 'autoconnect=yes'. That might result in an immediate activation of the connection.
+Do you still want to save? [yes] no
+nmcli> save
+Saving the connection with 'autoconnect=yes'. That might result in an immediate activation of the connection.
+Do you still want to save? [yes] yes
+Connection 'eth0' (704a5666-8cbd-4d89-b5f9-fa65a3dbc916) successfully saved.
+nmcli> quit
+~]$</pre>
+ The default action is to save the connection profile as persistent. If required, the profile can be held in memory only, until the next restart, by means of the <code class="command">save temporary</code> command.
+ </div></div></div><br class="example-break" /><h4 id="Locking_a_Profile_to_a_Specific_Device">Locking a Profile to a Specific Device</h4><div class="para">
+ To lock a profile to a specific interface device, the commands used in the examples above include the interface name. For example: <pre class="synopsis">nmcli connection add type ethernet con-name <em class="replaceable"><code>connection-name</code></em> ifname <em class="replaceable"><code>interface-name</code></em></pre> To make a profile usable for all compatible Ethernet interfaces, issue a command as follows: <pre class="synopsis">nmcli connection add type ethernet con-name <em class="replaceable"><code>connection-name</code></em> ifname "*"</pre> Note that you have to use the <code class="option">ifname</code> argument even if you do not want to set a specific interface. Use the wildcard character <code class="literal">*</code> to specify that the profile can be used with any compatible device.
+ </div><div class="para">
+ To lock a profile to a specific MAC address, use a command in the following format: <pre class="synopsis">nmcli connection add type ethernet con-name "<em class="replaceable"><code>connection-name</code></em>" ifname "*" mac 00:00:5E:00:53:00</pre>
+ </div><h4 id="Adding_a_Wi-Fi_Connection">Adding a Wi-Fi Connection</h4><div class="para">
+ To view the available Wi-Fi access points, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli dev wifi list</code>
+ SSID MODE CHAN RATE SIGNAL BARS SECURITY
+ FedoraTest Infra 11 54 MB/s 98 ▂▄▆█ WPA1
+ Red Hat Guest Infra 6 54 MB/s 97 ▂▄▆█ WPA2
+ Red Hat Infra 6 54 MB/s 77 ▂▄▆_ WPA2 802.1X
+* Red Hat Infra 40 54 MB/s 66 ▂▄▆_ WPA2 802.1X
+ VoIP Infra 1 54 MB/s 32 ▂▄__ WEP
+ MyCafe Infra 11 54 MB/s 39 ▂▄__ WPA2</pre>
+ </div><div class="para">
+ To create a Wi-Fi connection profile with static <code class="systemitem">IP</code> configuration, but allowing automatic <code class="systemitem">DNS</code> address assignment, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add con-name <em class="replaceable"><code>MyCafe</code></em> ifname wlan0 type wifi ssid MyCafe \</code>
+<code class="command">ip4 192.168.100.101/24 gw4 192.168.100.1</code></pre>
+ To set a WPA2 password, for example <span class="quote">“<span class="quote">caffeine</span>”</span>, issue commands as follows:
+<pre class="screen">~]$ <code class="command">nmcli con modify <em class="replaceable"><code>MyCafe</code></em> wifi-sec.key-mgmt wpa-psk</code>
+~]$ <code class="command">nmcli con modify <em class="replaceable"><code>MyCafe</code></em> wifi-sec.psk caffeine</code></pre>
+
+ </div><div class="para">
+ To change Wi-Fi state, issue a command in the following format:
+<pre class="screen">~]$ <code class="command">nmcli radio wifi [<span class="optional">on | off </span>]</code></pre>
+
+ </div><h4 id="Changing_a_Specific_Property">Changing a Specific Property</h4><div class="para">
+ To check a specific property, for example <code class="literal">mtu</code>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection show id '<em class="replaceable"><code>MyCafe</code></em>' | grep mtu</code>
+802-11-wireless.mtu: auto</pre>
+ To change the property of a setting, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection modify id '<em class="replaceable"><code>MyCafe</code></em>' 802-11-wireless.mtu 1350</code></pre>
+ To verify the change, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection show id '<em class="replaceable"><code>MyCafe</code></em>' | grep mtu</code>
+802-11-wireless.mtu: 1350</pre>
+
+ </div><div class="para">
+ Note that <span class="application"><strong>NetworkManager</strong></span> refers to parameters such as <code class="literal">802-3-ethernet</code> and <code class="literal">802-11-wireless</code> as the setting, and <code class="literal">mtu</code> as a property of the setting. See the <code class="filename">nm-settings(5)</code> man page for more information on properties and their settings.
+ </div></div><div class="section" id="sec-Configuring_Static_Routes_Using_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.3. Configuring Static Routes Using nmcli</h3></div></div></div><div class="para">
+ To configure static routes using the <span class="application"><strong>nmcli</strong></span> tool, the interactive editor mode must be used.
+ </div><div class="example" id="ex-Configuring_Static_Routes_Using_nmcli_Editor"><h6>Example 2.3. Configuring Static Routes Using nmcli Editor</h6><div class="example-contents"><div class="para">
+ To configure a static route for an Ethernet connection using the interactive editor, issue commands as follows:
+<pre class="screen">~]$ <code class="command">nmcli con edit type ethernet con-name <em class="replaceable"><code>eth0</code></em></code>
+
+===| nmcli interactive connection editor |===
+
+Adding a new '802-3-ethernet' connection
+
+Type 'help' or '?' for available commands.
+Type 'describe [>setting<.>prop<]' for detailed property description.
+
+You may edit the following settings: connection, 802-3-ethernet (ethernet), 802-1x, ipv4, ipv6, dcb
+nmcli> set ipv4.routes 192.168.122.0/24 10.10.10.1
+nmcli>
+nmcli> save persistent
+Saving the connection with 'autoconnect=yes'. That might result in an immediate activation of the connection.
+Do you still want to save? [yes] yes
+Connection 'eth0' (704a5666-8cbd-4d89-b5f9-fa65a3dbc916) successfully saved.
+nmcli> quit
+~]$</pre>
+ </div></div></div><br class="example-break" /></div></div><div class="section" id="sec-Configure_Networking-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.5. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources relevant to this chapter.
+ </div><div class="section" id="sec-Configure_Networking-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.5.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">ip(8)</code> man page — Describes the <span class="application"><strong>ip</strong></span> utility's command syntax.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nmcli(1)</code> man page — Describes <span class="application"><strong>NetworkManager</strong></span>'s command‐line tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nmcli-examples(5)</code> man page — Gives examples of <span class="application"><strong>nmcli</strong></span> commands.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nm-settings(5)</code> man page — Describes <span class="application"><strong>NetworkManager</strong></span> properties and their settings.
+ </div></li></ul></div></div><div class="section" id="sec-Configure_Networking_Online_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.5.2. Online Documentation</h3></div></div></div><div class="para">
+ <div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.rfc-editor.org/info/rfc1518"><em class="citetitle">RFC 1518</em></a> — Classless Inter-Domain Routing (CIDR)</span></dt><dd><div class="para">
+ Describes the CIDR Address Assignment and Aggregation Strategy, including variable-length subnetting.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.rfc-editor.org/info/rfc1918"><em class="citetitle">RFC 1918</em></a> — Address Allocation for Private Internets</span></dt><dd><div class="para">
+ Describes the range of <code class="systemitem">IPv4</code> addresses reserved for private use.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.rfc-editor.org/info/rfc3330"><em class="citetitle">RFC 3330</em></a> — Special-Use IPv4 Addresses</span></dt><dd><div class="para">
+ Describes the global and other specialized <code class="systemitem">IPv4</code> address blocks that have been assigned by the Internet Assigned Numbers Authority (IANA).
+ </div></dd></dl></div>
+ </div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-Configure_Host_Names" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 3. Configure Host Names</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sec_Understanding_Host_Names">3.1. Understanding Host Names</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Recommended_Naming_Practices">3.1.1. Recommended Naming Practices</a></span></dt></dl></dd><dt><span class="section"><a href="#sec_Configuring_Host_Names_Using_hostnamectl">3.2. Configuring Host Names Using hostnamectl</a></span></dt><dd><dl><dt><span class="section"><a href="#sec_View_All_the_Host_Names">3.2.1. View All the Host Names</a></span></dt><dt><span class="section"><a href="#sec_Set_All_the_Host_Names">3.2.2. Set All the Host Names</a></span></dt><dt><span class="section"><a href="#sec_Set_a_Particular_Host_Name">3.2.3. Set a Particular Host Name</a></span></dt><dt>
<span class="section"><a href="#sec_Clear_a_Particular_Host_Name">3.2.4. Clear a Particular Host Name</a></span></dt><dt><span class="section"><a href="#sec_Changing_Host_Names_Remotely">3.2.5. Changing Host Names Remotely</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Host_Names_Using_nmcli">3.3. Configuring Host Names Using nmcli</a></span></dt><dt><span class="section"><a href="#sec-additional_resources">3.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-hostnamectl-docs-inst">3.4.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-hostnamectl-Online_Documentation">3.4.2. Online Documentation</a></span></dt></dl></dd></dl></div><div class="section" id="sec_Understanding_Host_Names"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.1. Understanding Host Names</h2></div></div></div><div class="para">
+ There are three classes of <code class="systemitem">hostname</code>: static, pretty, and transient.
+ </div><div class="para">
+ The <span class="quote">“<span class="quote">static</span>”</span> host name is the traditional <code class="systemitem">hostname</code>, which can be chosen by the user, and is stored in the <code class="filename">/etc/hostname</code> file. The <span class="quote">“<span class="quote">transient</span>”</span> <code class="systemitem">hostname</code> is a dynamic host name maintained by the kernel. It is initialized to the static host name by default, whose value defaults to <span class="quote">“<span class="quote">localhost</span>”</span>. It can be changed by <code class="systemitem">DHCP</code> or <code class="systemitem">mDNS</code> at runtime. The <span class="quote">“<span class="quote">pretty</span>”</span> <code class="systemitem">hostname</code> is a free-form UTF8 host name for presentation to the user.
+ <div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ A host name can be a free-form string up to 64 characters in length. However, Red Hat recommends that both static and transient names match the <em class="firstterm">fully-qualified domain name</em> (<acronym class="acronym">FQDN</acronym>) used for the machine in <code class="systemitem">DNS</code>, such as <code class="systemitem">host.example.com</code>. It is also recommended that the static and transient names consists only of 7 bit ASCII lower-case characters, no spaces or dots, and limits itself to the format allowed for <code class="systemitem">DNS</code> domain name labels, even though this is not a strict requirement. Older specifications do not permit the underscore, and so their use is not recommended.
+ </div><div class="para">
+ The <span class="application"><strong>hostnamectl</strong></span> tool will enforce the following: Static and transient host names to consist of <code class="literal">a-z</code>, <code class="literal">A-Z</code>, <code class="literal">0-9</code>, <span class="quote">“<span class="quote"><code class="literal">-</code></span>”</span>, <span class="quote">“<span class="quote"><code class="literal">_</code></span>”</span> and <span class="quote">“<span class="quote"><code class="literal">.</code></span>”</span> only, to not begin or end in a dot, and to not have two dots immediately following each other. The size limit of 64 characters is enforced.
+ </div></div></div>
+
+ </div><div class="section" id="sec-Recommended_Naming_Practices"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.1.1. Recommended Naming Practices</h3></div></div></div><div class="para">
+ The Internet Corporation for Assigned Names and Numbers (ICANN) sometimes adds previously unregistered Top-Level Domains (such as <code class="systemitem">.yourcompany</code>) to the public register. Therefore, Red Hat strongly recommends that you do not use a domain name that is not delegated to you, even on a private network, as this can result in a domain name that resolves differently depending on network configuration. As a result, network resources can become unavailable. Using domain names that are not delegated to you also makes DNSSEC more difficult to deploy and maintain, as domain name collisions require manual configuration to enable DNSSEC validation. See the <a href="http://www.icann.org/en/help/name-collision/faqs">ICANN FAQ on domain name collision</a> for more information on this issue.
+ </div></div></div><div class="section" id="sec_Configuring_Host_Names_Using_hostnamectl"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.2. Configuring Host Names Using hostnamectl</h2></div></div></div><div class="para">
+ The <span class="application"><strong>hostnamectl</strong></span> tool is provided for administering the three separate classes of host names in use on a given system.
+ </div><div class="section" id="sec_View_All_the_Host_Names"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.1. View All the Host Names</h3></div></div></div><div class="para">
+ To view all the current host names, enter the following command:
+<pre class="screen">~]$ <code class="command">hostnamectl status</code></pre>
+ The <code class="option">status</code> option is implied by default if no option is given.
+ </div></div><div class="section" id="sec_Set_All_the_Host_Names"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.2. Set All the Host Names</h3></div></div></div><div class="para">
+ To set all the host names on a system, enter the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">hostnamectl set-hostname <em class="replaceable"><code>name</code></em></code></pre>
+ This will alter the pretty, static, and transient host names alike. The static and transient host names will be simplified forms of the pretty host name. Spaces will be replaced with <span class="quote">“<span class="quote"><code class="literal">-</code></span>”</span> and special characters will be removed.
+ </div></div><div class="section" id="sec_Set_a_Particular_Host_Name"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.3. Set a Particular Host Name</h3></div></div></div><div class="para">
+ To set a particular host name, enter the following command as <code class="systemitem">root</code> with the relevant option:
+<pre class="screen">~]# <code class="command">hostnamectl set-hostname <em class="replaceable"><code>name</code></em> [<span class="optional"><em class="replaceable"><code>option</code></em>...</span>]</code></pre>
+ Where <em class="replaceable"><code>option</code></em> is one or more of: <code class="option">--pretty</code>, <code class="option">--static</code>, and <code class="option">--transient</code>.
+ </div><div class="para">
+ If the <code class="option">--static</code> or <code class="option">--transient</code> options are used together with the <code class="option">--pretty</code> option, the static and transient host names will be simplified forms of the pretty host name. Spaces will be replaced with <span class="quote">“<span class="quote"><code class="literal">-</code></span>”</span> and special characters will be removed. If the <code class="option">--pretty</code> option is not given, no simplification takes place.
+ </div><div class="para">
+ When setting a pretty host name, remember to use the appropriate quotation marks if the host name contains spaces or a single quotation mark. For example:
+<pre class="screen">~]# <code class="command">hostnamectl set-hostname "Stephen's notebook" --pretty</code></pre>
+
+ </div></div><div class="section" id="sec_Clear_a_Particular_Host_Name"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.4. Clear a Particular Host Name</h3></div></div></div><div class="para">
+ To clear a particular host name and allow it to revert to the default, enter the following command as <code class="systemitem">root</code> with the relevant option:
+<pre class="screen">~]# <code class="command">hostnamectl set-hostname <em class="replaceable"><code>""</code></em> [<span class="optional"><em class="replaceable"><code>option</code></em>...</span>]</code></pre>
+ Where <em class="replaceable"><code>""</code></em> is a quoted empty string and where <em class="replaceable"><code>option</code></em> is one or more of: <code class="option">--pretty</code>, <code class="option">--static</code>, and <code class="option">--transient</code>.
+ </div></div><div class="section" id="sec_Changing_Host_Names_Remotely"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.5. Changing Host Names Remotely</h3></div></div></div><div class="para">
+ To execute a <code class="command">hostnamectl</code> command on a remote system, use the <code class="option">-H, --host</code> option as follows:
+<pre class="screen">~]# <code class="command">hostnamectl set-hostname <code class="option">-H</code> [<span class="optional"><em class="replaceable"><code>username</code></em></span>]@<em class="replaceable"><code>hostname</code></em></code></pre>
+ Where <em class="replaceable"><code>hostname</code></em> is the remote host you want to configure. The <em class="replaceable"><code>username</code></em> is optional. The <span class="application"><strong>hostnamectl</strong></span> tool will use <code class="systemitem">SSH</code> to connect to the remote system.
+ </div></div></div><div class="section" id="sec-Configuring_Host_Names_Using_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.3. Configuring Host Names Using nmcli</h2></div></div></div><div class="para">
+ The <span class="application"><strong>NetworkManager</strong></span> tool <span class="application"><strong>nmcli</strong></span> can be used to query and set the static host name in the <code class="filename">/etc/hostname</code> file. Note that at time of writing, changing the host name in this way will not be noticed by <span class="application"><strong>hostnamectl</strong></span>.
+ </div><div class="para">
+ To query the static host name, issue the following command:
+<pre class="screen">~]$ <code class="command">nmcli general hostname</code></pre>
+ To set the static host name to <em class="replaceable"><code>my-server</code></em>, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">nmcli general hostname <em class="replaceable"><code>my-server</code></em></code></pre>
+ To force <span class="application"><strong>hostnamectl</strong></span> to notice the change in the static host name, restart <code class="systemitem">hostnamed</code> as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl restart systemd-hostnamed</code></pre>
+
+ </div></div><div class="section" id="sec-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.4. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding <span class="application"><strong>hostnamectl</strong></span>.
+ </div><div class="section" id="sec-hostnamectl-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.4.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">hostnamectl(1)</code> man page — Describes <span class="application"><strong>hostnamectl</strong></span> including the commands and command options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">hostname(1)</code> man page — Contains an explanation of the <code class="command">hostname</code> and <code class="command">domainname</code> commands.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">hostname(5)</code> man page — Contains an explanation of the host name file, its contents, and use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">hostname(7)</code> man page — Contains an explanation of host name resolution.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">machine-info(5)</code> man page — Describes the local machine information file and the environment variables it contains.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">machine-id(5)</code> man page — Describes the local machine ID configuration file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">systemd-hostnamed.service(8)</code> man page — Describes the <code class="systemitem">systemd-hostnamed</code> system service used by <span class="application"><strong>hostnamectl</strong></span>.
+ </div></li></ul></div></div><div class="section" id="sec-hostnamectl-Online_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.4.2. Online Documentation</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.freedesktop.org/wiki/Software/systemd/hostnamed">http://www.freedesktop.org/wiki/Software/systemd/hostnamed</a></span></dt><dd><div class="para">
+ Information on <code class="systemitem">systemd-hostnamed</code>.
+ </div></dd></dl></div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-Configure_Network_Bonding" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 4. Configure Network Bonding</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sec-Bond-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces">4.1. Understanding the Default Behavior of Master and Slave Interfaces</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Bond_Connection_Using_a_GUI">4.2. Creating a Bond Connection Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_Bond_Connection">4.2.1. Establishing a Bond Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Network_Bonding_Using_the_Command_Line_Interface">4.3. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Check_if_Bonding_Kernel_Module_is_In
stalled">4.3.1. Check if Bonding Kernel Module is Installed</a></span></dt><dt><span class="section"><a href="#sec-Create_a_Channel_Bonding_Interface">4.3.2. Create a Channel Bonding Interface</a></span></dt><dt><span class="section"><a href="#sec-Creating_SLAVE_Interfaces">4.3.3. Creating SLAVE Interfaces</a></span></dt><dt><span class="section"><a href="#sec-Activating_a_Channel_Bond">4.3.4. Activating a Channel Bond</a></span></dt><dt><span class="section"><a href="#sec-Creating_Multiple_Bonds">4.3.5. Creating Multiple Bonds</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_Channel_Bonding">4.4. Using Channel Bonding</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-modules-bonding-directives">4.4.1. Bonding Module Directives</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli">4.5. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dt><span class=
"section"><a href="#sec-Configure_Network_Bonding-additional_resources">4.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configure_Network_Bonding-docs-inst">4.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-Configure_Network_Bonding_Online_Documentation">4.6.2. Online Documentation</a></span></dt></dl></dd></dl></div><div class="para">
+ Fedora allows administrators to bind multiple network interfaces together into a single, bonded, channel. Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The use of direct cable connections without network switches is not supported for bonding. The failover mechanisms described here will not work as expected without the presence of network switches.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The active-backup, balance-tlb and balance-alb modes do not require any specific configuration of the switch. Other bonding modes require configuring the switch to aggregate the links. For example, a Cisco switch requires EtherChannel for Modes 0, 2, and 3, but for Mode 4 LACP and EtherChannel are required. See the documentation supplied with your switch and see <a href="https://www.kernel.org/doc/Documentation/networking/bonding.txt">https://www.kernel.org/doc/Documentation/networking/bonding.txt</a>
+ </div></div></div><div class="section" id="sec-Bond-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.1. Understanding the Default Behavior of Master and Slave Interfaces</h2></div></div></div><div class="para">
+ When controlling bonded slave interfaces using the <code class="systemitem">NetworkManager</code> daemon, and especially when fault finding, keep the following in mind:
+ <div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Starting the master interface does not automatically start the slave interfaces.
+ </div></li><li class="listitem"><div class="para">
+ Starting a slave interface always starts the master interface.
+ </div></li><li class="listitem"><div class="para">
+ Stopping the master interface also stops the slave interfaces.
+ </div></li><li class="listitem"><div class="para">
+ A master without slaves can start static <code class="systemitem">IP</code> connections.
+ </div></li><li class="listitem"><div class="para">
+ A master without slaves waits for slaves when starting <code class="systemitem">DHCP</code> connections.
+ </div></li><li class="listitem"><div class="para">
+ A master with a <code class="systemitem">DHCP</code> connection waiting for slaves completes when a slave with a carrier is added.
+ </div></li><li class="listitem"><div class="para">
+ A master with a <code class="systemitem">DHCP</code> connection waiting for slaves continues waiting when a slave without a carrier is added.
+ </div></li></ol></div>
+ </div></div><div class="section" id="sec-Creating_a_Bond_Connection_Using_a_GUI"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Creating a Bond Connection Using a GUI</h2></div></div></div><div class="para">
+ You can use the GNOME <span class="application"><strong>control-center</strong></span> utility to direct <span class="application"><strong>NetworkManager</strong></span> to create a Bond from two or more Wired or InfiniBand connections. It is not necessary to create the connections to be bonded first. They can be configured as part of the process to configure the bond. You must have the MAC addresses of the interfaces available in order to complete the configuration process.
+ </div><div class="section" id="sec-Establishing_a_Bond_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.2.1. Establishing a Bond Connection</h3></div></div></div><div class="procedure" id="procedure-Adding_a_New_Bond_Connection"><h6>Procedure 4.1. Adding a New Bond Connection</h6><div class="para">
+ You can configure a Bond connection by opening the <span class="guilabel"><strong>Network</strong></span> window, clicking the plus symbol, and selecting <span class="guilabel"><strong>Bond</strong></span> from the list.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Click the plus symbol to open the selection list. Select <span class="guilabel"><strong>Bond</strong></span>. The <span class="guilabel"><strong>Editing Bond connection <em class="replaceable"><code>1</code></em></strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ On the <span class="guilabel"><strong>Bond</strong></span> tab, click <span class="guibutton"><strong>Add</strong></span> and select the type of interface you want to use with the bond connection. Click the <span class="guibutton"><strong>Create</strong></span> button. Note that the dialog to select the slave type only comes up when you create the first slave; after that, it will automatically use that same type for all further slaves.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Editing bond0 slave 1</strong></span> window appears. Use the <span class="guilabel"><strong>Device MAC address</strong></span> drop-down menu to select the MAC address of the interface to be bonded. The first slave's MAC address will be used as the MAC address for the bond interface. If required, enter a clone MAC address to be used as the bond's MAC address. Click the <span class="guibutton"><strong>Save</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ The name of the bonded slave appears in the <span class="guilabel"><strong>Bonded connections</strong></span> window. Click the <span class="guibutton"><strong>Add</strong></span> button to add further slave connections.
+ </div></li><li class="step"><div class="para">
+ Review and confirm the settings and then click the <span class="guilabel"><strong>Save</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Edit the bond-specific settings by referring to <a class="xref" href="#sec-Configuring_the_Bond_Tab">Section 4.2.1.1, “Configuring the Bond Tab”</a> below.
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_Bond_Connection"><h6>Procedure 4.2. Editing an Existing Bond Connection</h6><div class="para">
+ Follow these steps to edit an existing bond connection.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the connection you want to edit and click the <span class="guilabel"><strong>Options</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>General</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Configure the connection name, auto-connect behavior, and availability settings.
+ </div><div class="para">
+ Five settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types, see the <span class="guilabel"><strong>General</strong></span> tab:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the menu of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to this network when it is available</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="#sec-Connecting_to_a_Network_Automatically">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>All users may connect to this network</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="#sec-System-wide_and_Private_Connection_Profiles">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to VPN when using this connection</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to a VPN connection when it is available. Select the VPN from the drop-down menu.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Firewall Zone</strong></span> — Select the firewall zone from the drop-down menu.
+ </div></li></ul></div></li><li class="step"><div class="para">
+ Edit the bond-specific settings by referring to <a class="xref" href="#sec-Configuring_the_Bond_Tab">Section 4.2.1.1, “Configuring the Bond Tab”</a> below.
+ </div></li></ol></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-bond">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your bond connection, click the <span class="guibutton"><strong>Save</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network</strong></span> window and clicking <span class="guilabel"><strong>Options</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv6</code> settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv6_Settings">Section 2.2.10.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div><div class="section" id="sec-Configuring_the_Bond_Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">4.2.1.1. Configuring the Bond Tab</h4></div></div></div><div class="para">
+ If you have already added a new bond connection (refer to <a class="xref" href="#procedure-Adding_a_New_Bond_Connection">Procedure 4.1, “Adding a New Bond Connection”</a> for instructions), you can edit the <span class="guilabel"><strong>Bond</strong></span> tab to set the load sharing mode and the type of link monitoring to use to detect failures of a slave connection.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Mode</strong></span> </span></dt><dd><div class="para">
+ The mode that is used to share traffic over the slave connections which make up the bond. The default is <span class="guilabel"><strong>Round-robin</strong></span>. Other load sharing modes, such as <code class="systemitem">802.3ad</code>, can be selected by means of the drop-down list.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Link Monitoring</strong></span> </span></dt><dd><div class="para">
+ The method of monitoring the slaves ability to carry network traffic.
+ </div></dd></dl></div><div class="para">
+ The following modes of load sharing are selectable from the <span class="guilabel"><strong>Mode</strong></span> drop-down list:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Round-robin</strong></span> </span></dt><dd><div class="para">
+ Sets a round-robin policy for fault tolerance and load balancing. Transmissions are received and sent out sequentially on each bonded slave interface beginning with the first one available. This mode might not work behind a bridge with virtual machines without additional switch configuration.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Active backup</strong></span> </span></dt><dd><div class="para">
+ Sets an active-backup policy for fault tolerance. Transmissions are received and sent out via the first available bonded slave interface. Another bonded slave interface is only used if the active bonded slave interface fails. Note that this is the only mode available for bonds of InfiniBand devices.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>XOR</strong></span> </span></dt><dd><div class="para">
+ Sets an XOR (exclusive-or) policy. Transmissions are based on the selected hash policy. The default is to derive a hash by XOR of the source and destination MAC addresses multiplied by the modulo of the number of slave interfaces. In this mode traffic destined for specific peers will always be sent over the same interface. As the destination is determined by the MAC addresses this method works best for traffic to peers on the same link or local network. If traffic has to pass through a single router then this mode of traffic balancing will be suboptimal.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Broadcast</strong></span> </span></dt><dd><div class="para">
+ Sets a broadcast policy for fault tolerance. All transmissions are sent on all slave interfaces. This mode might not work behind a bridge with virtual machines without additional switch configuration.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>802.3ad</strong></span> </span></dt><dd><div class="para">
+ Sets an IEEE <code class="systemitem">802.3ad</code> dynamic link aggregation policy. Creates aggregation groups that share the same speed and duplex settings. Transmits and receives on all slaves in the active aggregator. Requires a network switch that is <code class="systemitem">802.3ad</code> compliant.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Adaptive transmit load balancing</strong></span> </span></dt><dd><div class="para">
+ Sets an adaptive Transmit Load Balancing (TLB) policy for fault tolerance and load balancing. The outgoing traffic is distributed according to the current load on each slave interface. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed slave. This mode is only suitable for local addresses known to the kernel bonding module and therefore cannot be used behind a bridge with virtual machines.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Adaptive load balancing</strong></span> </span></dt><dd><div class="para">
+ Sets an Adaptive Load Balancing (ALB) policy for fault tolerance and load balancing. Includes transmit and receive load balancing for <code class="systemitem">IPv4</code> traffic. Receive load balancing is achieved through <code class="systemitem">ARP</code> negotiation. This mode is only suitable for local addresses known to the kernel bonding module and therefore cannot be used behind a bridge with virtual machines.
+ </div></dd></dl></div><div class="para">
+ The following types of link monitoring can be selected from the <span class="guilabel"><strong>Link Monitoring</strong></span> drop-down list. It is a good idea to test which channel bonding module parameters work best for your bonded interfaces.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>MII (Media Independent Interface)</strong></span> </span></dt><dd><div class="para">
+ The state of the carrier wave of the interface is monitored. This can be done by querying the driver, by querying MII registers directly, or by using <span class="application"><strong>ethtool</strong></span> to query the device. Three options are available:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Monitoring Frequency</strong></span> </span></dt><dd><div class="para">
+ The time interval, in milliseconds, between querying the driver or MII registers.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Link up delay</strong></span> </span></dt><dd><div class="para">
+ The time in milliseconds to wait before attempting to use a link that has been reported as up. This delay can be used if some gratuitous <code class="systemitem">ARP</code> requests are lost in the period immediately following the link being reported as <span class="quote">“<span class="quote">up</span>”</span>. This can happen during switch initialization for example.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Link down delay</strong></span> </span></dt><dd><div class="para">
+ The time in milliseconds to wait before changing to another link when a previously active link has been reported as <span class="quote">“<span class="quote">down</span>”</span>. This delay can be used if an attached switch takes a relatively long time to change to backup mode.
+ </div></dd></dl></div></dd></dl></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>ARP</strong></span> </span></dt><dd><div class="para">
+ The address resolution protocol (<code class="systemitem">ARP</code>) is used to probe one or more peers to determine how well the link-layer connections are working. It is dependent on the device driver providing the transmit start time and the last receive time.
+ </div><div class="para">
+ Two options are available:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Monitoring Frequency</strong></span> </span></dt><dd><div class="para">
+ The time interval, in milliseconds, between sending <code class="systemitem">ARP</code> requests.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>ARP targets</strong></span> </span></dt><dd><div class="para">
+ A comma separated list of <code class="systemitem">IP</code> addresses to send <code class="systemitem">ARP</code> requests to.
+ </div></dd></dl></div></dd></dl></div></div></div></div><div class="section" id="sec-Network_Bonding_Using_the_Command_Line_Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. Using the Command Line Interface (CLI)</h2></div></div></div><div class="para">
+ A bond is created using the <code class="filename">bonding</code> kernel module and a special network interface called a <em class="firstterm">channel bonding interface</em>.
+ </div><div class="section" id="sec-Check_if_Bonding_Kernel_Module_is_Installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.1. Check if Bonding Kernel Module is Installed</h3></div></div></div><div class="para">
+ In Fedora, the bonding module is not loaded by default. You can load the module by issuing the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">modprobe --first-time bonding</code></pre>
+ This activation will not persist across system restarts. See the <em class="citetitle">Fedora 20 System Administrator's Guide</em> for an explanation of persistent module loading. Note that given a correct configuration file using the <code class="command">BONDING_OPTS</code> directive, the bonding module will be loaded as required and therefore does not need to be loaded separately.
+ </div><div class="para">
+ To display information about the module, issue the following command:
+<pre class="screen">~]$ <code class="command">modinfo bonding</code></pre>
+ See the <code class="filename">modprobe(8)</code> man page for more command options.
+ </div></div><div class="section" id="sec-Create_a_Channel_Bonding_Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.2. Create a Channel Bonding Interface</h3></div></div></div><div class="para">
+ To create a channel bonding interface, create a file in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory called <code class="filename">ifcfg-bond<em class="replaceable"><code>N</code></em></code>, replacing <em class="replaceable"><code>N</code></em> with the number for the interface, such as <code class="filename">0</code>.
+ </div><div class="para">
+ The contents of the file can be based on a configuration file for whatever type of interface is getting bonded, such as an Ethernet interface. The essential differences are that the <code class="option">DEVICE</code> directive is <code class="option">bond<em class="replaceable"><code>N</code></em></code>, replacing <em class="replaceable"><code>N</code></em> with the number for the interface, and <code class="command">TYPE=Bond</code>. In addition, set <code class="command">BONDING_MASTER=yes</code>.
+ </div><div class="example" id="ex-Example_ifcfg-bond0_Interface_Configuration_File"><h6>Example 4.1. Example ifcfg-bond0 Interface Configuration File</h6><div class="example-contents"><div class="para">
+ An example of a channel bonding interface.
+ </div><pre class="programlisting">DEVICE=bond0
+NAME=bond0
+TYPE=Bond
+BONDING_MASTER=yes
+IPADDR=192.168.1.1
+PREFIX=24
+ONBOOT=yes
+BOOTPROTO=none
+BONDING_OPTS="<em class="replaceable"><code>bonding parameters separated by spaces</code></em>"</pre><div class="para">
+ The NAME directive is useful for naming the connection profile in <span class="application"><strong>NetworkManager</strong></span>. ONBOOT says whether the profile should be started when booting (or more generally, when auto-connecting a device).
+ </div></div></div><br class="example-break" /><div class="important"><div class="admonition_header"><h2>Put all Bonding Module Parameters in ifcfg-bondN Files</h2></div><div class="admonition"><div class="para">
+ Parameters for the bonding kernel module must be specified as a space-separated list in the <code class="option">BONDING_OPTS="<em class="replaceable"><code>bonding parameters</code></em>"</code> directive in the <code class="filename">ifcfg-bond<em class="replaceable"><code>N</code></em></code> interface file. Do <span class="emphasis"><em>not</em></span> specify options for the bonding device in <code class="filename">/etc/modprobe.d/<em class="replaceable"><code>bonding</code></em>.conf</code>, or in the deprecated <code class="filename">/etc/modprobe.conf</code> file.
+ </div><div class="para">
+ The <code class="option">max_bonds</code> parameter is not interface specific and should not be set when using <code class="filename">ifcfg-bond<em class="replaceable"><code>N</code></em></code> files with the <code class="command">BONDING_OPTS</code> directive as this directive will cause the network scripts to create the bond interfaces as required.
+ </div><div class="para">
+ For further instructions and advice on configuring the bonding module and to view the list of bonding parameters, see <a class="xref" href="#sec-Using_Channel_Bonding">Section 4.4, “Using Channel Bonding”</a>.
+ </div></div></div></div><div class="section" id="sec-Creating_SLAVE_Interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.3. Creating SLAVE Interfaces</h3></div></div></div><div class="para">
+ The channel bonding interface is the <span class="quote">“<span class="quote">master</span>”</span> and the interfaces to be bonded are referred to as the <span class="quote">“<span class="quote">slaves</span>”</span>. After the channel bonding interface is created, the network interfaces to be bound together must be configured by adding the <code class="option">MASTER</code> and <code class="option">SLAVE</code> directives to the configuration files of the slaves. The configuration files for each of the slave interfaces can be nearly identical.
+ </div><div class="example" id="ex-Example_Slave_Interface_Configuration_File"><h6>Example 4.2. Example Slave Interface Configuration File</h6><div class="example-contents"><div class="para">
+ For example, if two Ethernet interfaces are being channel bonded, <code class="literal">eth0</code> and <code class="literal">eth1</code>, they can both look like the following example:
+ </div><pre class="programlisting">DEVICE=eth<em class="replaceable"><code>N</code></em>
+NAME=bond0-slave
+TYPE=Ethernet
+BOOTPROTO=none
+ONBOOT=yes
+MASTER=bond0
+SLAVE=yes</pre><div class="para">
+ In this example, replace <em class="replaceable"><code>N</code></em> with the numerical value for the interface. Note that if more than one profile or configuration file exists with ONBOOT=yes for an interface, they may race with each other and a plain TYPE=Ethernet profile may be activated instead of a bond slave.
+ </div></div></div><br class="example-break" /></div><div class="section" id="sec-Activating_a_Channel_Bond"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.4. Activating a Channel Bond</h3></div></div></div><div class="para">
+ To activate a bond, bring up all the slaves. As <code class="systemitem">root</code>, issue the following commands:
+<pre class="screen">~]# <code class="command">ifup ifcfg-eth0</code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/7)</pre>
+
+<pre class="screen">~]# <code class="command">ifup ifcfg-eth1</code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/8)</pre>
+ </div><div class="para">
+ Note that if editing interface files for interfaces which are currently <span class="quote">“<span class="quote">up</span>”</span>, set them down first as follows: <pre class="synopsis">ifdown eth<em class="replaceable"><code>N</code></em></pre> Then when complete, bring up all the slaves, which will bring up the bond (provided it was not set <span class="quote">“<span class="quote">down</span>”</span>).
+ </div><div class="para">
+ To make <span class="application"><strong>NetworkManager</strong></span> aware of the changes, issue a command for every changed interface as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">nmcli con load /etc/sysconfig/network-scripts/ifcfg-<em class="replaceable"><code>device</code></em></code></pre>
+ Alternatively, to reload all interfaces:
+<pre class="screen">~]# <code class="command">nmcli con reload</code></pre>
+ The default behavior is for <span class="application"><strong>NetworkManager</strong></span> not to be aware of the changes and to continue using the old configuration data. The is set by the <code class="option">monitor-connection-files</code> option in the <code class="filename">NetworkManager.conf</code> file. See the <code class="filename">NetworkManager.conf(5)</code> manual page for more information.
+ </div><div class="para">
+ To view the status of the bond interface, issue the following command:
+<pre class="screen">~]# <code class="command">ip link show</code>
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 1000
+ link/ether 52:54:00:e9:ce:d2 brd ff:ff:ff:ff:ff:ff
+3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 1000
+ link/ether 52:54:00:38:a6:4c brd ff:ff:ff:ff:ff:ff
+4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT
+ link/ether 52:54:00:38:a6:4c brd ff:ff:ff:ff:ff:ff</pre>
+
+ </div></div><div class="section" id="sec-Creating_Multiple_Bonds"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.5. Creating Multiple Bonds</h3></div></div></div><div class="para">
+ In Fedora 20, for each bond a channel bonding interface is created including the <code class="command">BONDING_OPTS</code> directive. This configuration method is used so that multiple bonding devices can have different configurations. To create multiple channel bonding interfaces, proceed as follows:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Create multiple <code class="filename">ifcfg-bond<em class="replaceable"><code>N</code></em></code> files with the <code class="command">BONDING_OPTS</code> directive; this directive will cause the network scripts to create the bond interfaces as required.
+ </div></li><li class="listitem"><div class="para">
+ Create, or edit existing, interface configuration files to be bonded and include the <code class="command">SLAVE</code> directive.
+ </div></li><li class="listitem"><div class="para">
+ Assign the interfaces to be bonded, the slave interfaces, to the channel bonding interfaces by means of the <code class="command">MASTER</code> directive.
+ </div></li></ul></div>
+
+ </div><div class="example" id="ex-Example-multiple-bondN_interface_configuration_files"><h6>Example 4.3. Example multiple ifcfg-bondN interface configuration files</h6><div class="example-contents"><div class="para">
+ The following is an example of a channel bonding interface configuration file:
+<pre class="programlisting">DEVICE=bondN
+NAME=bondN
+TYPE=Bond
+BONDING_MASTER=yes
+IPADDR=192.168.1.1
+PREFIX=24
+ONBOOT=yes
+BOOTPROTO=none
+BONDING_OPTS="<em class="replaceable"><code>bonding parameters separated by spaces</code></em>"</pre>
+ </div><div class="para">
+ In this example, replace <em class="replaceable"><code>N</code></em> with the number for the bond interface. For example, to create two bonds create two configuration files, <code class="filename">ifcfg-bond0</code> and <code class="filename">ifcfg-bond1</code>, with appropriate <code class="systemitem">IP</code> addresses.
+ </div></div></div><br class="example-break" /><div class="para">
+ Create the interfaces to be bonded as per <a class="xref" href="#ex-Example_Slave_Interface_Configuration_File">Example 4.2, “Example Slave Interface Configuration File”</a> and assign them to the bond interfaces as required using the <code class="command">MASTER=bond<em class="replaceable"><code>N</code></em></code> directive. For example, continuing on from the example above, if two interfaces per bond are required, then for two bonds create four interface configuration files and assign the first two using <code class="command">MASTER=bond<em class="replaceable"><code>0</code></em></code> and the next two using <code class="command">MASTER=bond<em class="replaceable"><code>1</code></em></code>.
+ </div></div></div><div class="section" id="sec-Using_Channel_Bonding"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.4. Using Channel Bonding</h2></div></div></div><a id="idm225417686912" class="indexterm"></a><a id="idm225417684992" class="indexterm"></a><a id="idm225453363488" class="indexterm"></a><a id="idm225453362048" class="indexterm"></a><a id="idm225447726848" class="indexterm"></a><a id="idm225447725440" class="indexterm"></a><a id="idm225447724000" class="indexterm"></a><div class="para">
+ To enhance performance, adjust available module options to ascertain what combination works best. Pay particular attention to the <code class="command">miimon</code> or <code class="command">arp_interval</code> and the <code class="command">arp_ip_target</code> parameters. See <a class="xref" href="#s3-modules-bonding-directives">Section 4.4.1, “Bonding Module Directives”</a> for a list of available options and how to quickly determine the best ones for your bonded interface.
+ </div><div class="section" id="s3-modules-bonding-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.4.1. Bonding Module Directives</h3></div></div></div><a id="idm225465674832" class="indexterm"></a><a id="idm225465672944" class="indexterm"></a><a id="idm225463196528" class="indexterm"></a><div class="para">
+ It is a good idea to test which channel bonding module parameters work best for your bonded interfaces before adding them to the <code class="option">BONDING_OPTS="<em class="replaceable"><code>bonding parameters</code></em>"</code> directive in your bonding interface configuration file (<code class="filename">ifcfg-bond0</code> for example). Parameters to bonded interfaces can be configured without unloading (and reloading) the bonding module by manipulating files in the <code class="systemitem">sysfs</code> file system.
+ </div><div class="para">
+ <code class="systemitem">sysfs</code> is a virtual file system that represents kernel objects as directories, files and symbolic links. <code class="systemitem">sysfs</code> can be used to query for information about kernel objects, and can also manipulate those objects through the use of normal file system commands. The <code class="systemitem">sysfs</code> virtual file system is mounted under the <code class="filename">/sys/</code> directory. All bonding interfaces can be configured dynamically by interacting with and manipulating files under the <code class="filename">/sys/class/net/</code> directory.
+ </div><div class="para">
+ In order to determine the best parameters for your bonding interface, create a channel bonding interface file such as <code class="filename">ifcfg-bond0</code> by following the instructions in <a class="xref" href="#sec-Create_a_Channel_Bonding_Interface">Section 4.3.2, “Create a Channel Bonding Interface”</a>. Insert the <code class="option">SLAVE=yes</code> and <code class="option">MASTER=bond0</code> directives in the configuration files for each interface bonded to <code class="literal">bond0</code>. Once this is completed, you can proceed to testing the parameters.
+ </div><div class="para">
+ First, bring up the bond you created by running <code class="command">ifup <code class="option">bond<em class="replaceable"><code>N</code></em></code></code> as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">ifup bond0</code></pre><div class="para">
+ If you have correctly created the <code class="filename">ifcfg-bond0</code> bonding interface file, you will be able to see <code class="computeroutput">bond0</code> listed in the output of running <code class="command"> ip link show</code> as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">ip link show</code>
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 1000
+ link/ether 52:54:00:e9:ce:d2 brd ff:ff:ff:ff:ff:ff
+3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 1000
+ link/ether 52:54:00:38:a6:4c brd ff:ff:ff:ff:ff:ff
+4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT
+ link/ether 52:54:00:38:a6:4c brd ff:ff:ff:ff:ff:ff</pre><div class="para">
+ To view all existing bonds, even if they are not up, run:
+ </div><pre class="screen">~]$ <code class="command">cat /sys/class/net/bonding_masters</code>
+bond0</pre><div class="para">
+ You can configure each bond individually by manipulating the files located in the <code class="filename">/sys/class/net/bond<em class="replaceable"><code>N</code></em>/bonding/</code> directory. First, the bond you are configuring must be taken down:
+ </div><pre class="screen">~]# <code class="command">ifdown bond0</code>
+</pre><div class="para">
+ As an example, to enable MII monitoring on bond0 with a 1 second interval, run as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">echo 1000 > /sys/class/net/bond0/bonding/miimon</code>
+</pre><div class="para">
+ To configure bond0 for <em class="parameter"><code>balance-alb</code></em> mode, run either:
+ </div><pre class="screen">~]# <code class="command">echo 6 > /sys/class/net/bond0/bonding/mode</code>
+</pre><div class="para">
+ ...or, using the name of the mode:
+ </div><pre class="screen">~]# <code class="command">echo balance-alb > /sys/class/net/bond0/bonding/mode</code>
+</pre><div class="para">
+ After configuring options for the bond in question, you can bring it up and test it by running <code class="command">ifup bond<em class="replaceable"><code>N</code></em></code>. If you decide to change the options, take the interface down, modify its parameters using <code class="systemitem">sysfs</code>, bring it back up, and re-test.
+ </div><div class="para">
+ Once you have determined the best set of parameters for your bond, add those parameters as a space-separated list to the <em class="parameter"><code>BONDING_OPTS=</code></em> directive of the <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond<em class="replaceable"><code>N</code></em> </code> file for the bonding interface you are configuring. Whenever that bond is brought up (for example, by the system during the boot sequence if the <em class="parameter"><code>ONBOOT=yes</code></em> directive is set), the bonding options specified in the <em class="parameter"><code>BONDING_OPTS</code></em> will take effect for that bond.
+ </div><div class="para">
+ The following list provides the names of many of the more common channel bonding parameters, along with a description of what they do. For more information, see the brief descriptions for each <code class="computeroutput">parm</code> in <code class="command">modinfo bonding</code> output, or for more detailed information, see <a href="https://www.kernel.org/doc/Documentation/networking/bonding.txt">https://www.kernel.org/doc/Documentation/networking/bonding.txt</a>.
+ </div><div class="variablelist"><h6>Bonding Interface Parameters</h6><dl class="variablelist compact"><dt class="varlistentry"><span class="term"> <code class="literal">ad_select=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Specifies the 802.3ad aggregation selection logic to use. Possible values are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>stable</code></strong> or <strong class="userinput"><code>0</code></strong> — Default setting. The active aggregator is chosen by largest aggregate bandwidth. Reselection of the active aggregator occurs only when all slaves of the active aggregator are down or if the active aggregator has no slaves.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>bandwidth</code></strong> or <strong class="userinput"><code>1</code></strong> — The active aggregator is chosen by largest aggregate bandwidth. Reselection occurs if:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ A slave is added to or removed from the bond;
+ </div></li><li class="listitem"><div class="para">
+ Any slave's link state changes;
+ </div></li><li class="listitem"><div class="para">
+ Any slave's 802.3ad association state changes;
+ </div></li><li class="listitem"><div class="para">
+ The bond's administrative state changes to up.
+ </div></li></ul></div>
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>count</code></strong> or <strong class="userinput"><code>2</code></strong> — The active aggregator is chosen by the largest number of slaves. Reselection occurs as described for the <code class="option">bandwidth</code> setting above.
+ </div></li></ul></div>
+ The <code class="option">bandwidth</code> and <code class="option">count</code> selection policies permit failover of 802.3ad aggregations when partial failure of the active aggregator occurs. This keeps the aggregator with the highest availability, either in bandwidth or in number of slaves, active at all times.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">arp_interval=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies, in milliseconds, how often <code class="systemitem">ARP</code> monitoring occurs.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ It is essential that both <code class="literal">arp_interval</code> and <code class="literal">arp_ip_target</code> parameters are specified, or, alternatively, the <code class="literal">miimon</code> parameter is specified. Failure to do so can cause degradation of network performance in the event that a link fails.
+ </div></div></div><div class="para">
+ If using this setting while in <code class="literal">mode=0</code> or <code class="literal">mode=2</code> (the two load-balancing modes), the network switch must be configured to distribute packets evenly across the NICs. For more information on how to accomplish this, see <a href="https://www.kernel.org/doc/Documentation/networking/bonding.txt">https://www.kernel.org/doc/Documentation/networking/bonding.txt</a>.
+ </div><div class="para">
+ The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">arp_ip_target=<em class="replaceable"><code>ip_address</code></em>[<span class="optional">,<em class="replaceable"><code>ip_address_2</code></em>,…<em class="replaceable"><code>ip_address_16</code></em></span>] </code> </span></dt><dd><div class="para">
+ Specifies the target <code class="systemitem">IP</code> address of <code class="systemitem">ARP</code> requests when the <code class="literal">arp_interval</code> parameter is enabled. Up to 16 <code class="systemitem">IP</code> addresses can be specified in a comma separated list.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">arp_validate=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Validate source/distribution of <code class="systemitem">ARP</code> probes; default is <strong class="userinput"><code>none</code></strong>. Other valid values are <strong class="userinput"><code>active</code></strong>, <strong class="userinput"><code>backup</code></strong>, and <strong class="userinput"><code>all</code></strong>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">downdelay=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how long to wait after link failure before disabling the link. The value must be a multiple of the value specified in the <code class="literal">miimon</code> parameter. The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">fail_over_mac=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Specifies whether active-backup mode should set all slaves to the same MAC address at enslavement (the traditional behavior), or, when enabled, perform special handling of the bond's MAC address in accordance with the selected policy. Possible values are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>none</code></strong> or <strong class="userinput"><code>0</code></strong> — Default setting. This setting disables <code class="literal">fail_over_mac</code>, and causes bonding to set all slaves of an active-backup bond to the same MAC address at enslavement time.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>active</code></strong> or <strong class="userinput"><code>1</code></strong> — The <span class="quote">“<span class="quote">active</span>”</span> <code class="literal">fail_over_mac</code> policy indicates that the MAC address of the bond should always be the MAC address of the currently active slave. The MAC address of the slaves is not changed; instead, the MAC address of the bond changes during a failover.
+ </div><div class="para">
+ This policy is useful for devices that cannot ever alter their MAC address, or for devices that refuse incoming broadcasts with their own source MAC (which interferes with the ARP monitor). The disadvantage of this policy is that every device on the network must be updated via gratuitous ARP, as opposed to the normal method of switches snooping incoming traffic to update their ARP tables. If the gratuitous ARP is lost, communication may be disrupted.
+ </div><div class="para">
+ When this policy is used in conjunction with the MII monitor, devices which assert link up prior to being able to actually transmit and receive are particularly susceptible to loss of the gratuitous ARP, and an appropriate updelay setting may be required.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>follow</code></strong> or <strong class="userinput"><code>2</code></strong> — The <span class="quote">“<span class="quote">follow</span>”</span> <code class="literal">fail_over_mac</code> policy causes the MAC address of the bond to be selected normally (normally the MAC address of the first slave added to the bond). However, the second and subsequent slaves are not set to this MAC address while they are in a backup role; a slave is programmed with the bond's MAC address at failover time (and the formerly active slave receives the newly active slave's MAC address).
+ </div><div class="para">
+ This policy is useful for multiport devices that either become confused or incur a performance penalty when multiple ports are programmed with the same MAC address.
+ </div></li></ul></div>
+ </div></dd><dt class="varlistentry"><span class="term">lacp_rate=<em class="replaceable"><code>value</code></em> </span></dt><dd><div class="para">
+ Specifies the rate at which link partners should transmit LACPDU packets in 802.3ad mode. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>slow</code></strong> or <strong class="userinput"><code>0</code></strong> — Default setting. This specifies that partners should transmit LACPDUs every 30 seconds.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>fast</code></strong> or <strong class="userinput"><code>1</code></strong> — Specifies that partners should transmit LACPDUs every 1 second.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">miimon=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how often MII link monitoring occurs. This is useful if high availability is required because MII is used to verify that the NIC is active. To verify that the driver for a particular NIC supports the MII tool, type the following command as root:
+ </div><pre class="screen">~]# <code class="command">ethtool <em class="replaceable"><code>interface_name</code></em> | grep "Link detected:"</code>
+</pre><div class="para">
+ In this command, replace <em class="replaceable"><code>interface_name</code></em>> with the name of the device interface, such as <strong class="userinput"><code>eth0</code></strong>, not the bond interface. If MII is supported, the command returns:
+ </div><pre class="screen">Link detected: yes</pre><div class="para">
+ If using a bonded interface for high availability, the module for each NIC must support MII. Setting the value to <strong class="userinput"><code>0</code></strong> (the default), turns this feature off. When configuring this setting, a good starting point for this parameter is <strong class="userinput"><code>100</code></strong>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ It is essential that both <code class="literal">arp_interval</code> and <code class="literal">arp_ip_target</code> parameters are specified, or, alternatively, the <code class="literal">miimon</code> parameter is specified. Failure to do so can cause degradation of network performance in the event that a link fails.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">mode=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Allows you to specify the bonding policy. The <em class="replaceable"><code>value</code></em> can be one of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-rr</code></strong> or <strong class="userinput"><code>0</code></strong> — Sets a round-robin policy for fault tolerance and load balancing. Transmissions are received and sent out sequentially on each bonded slave interface beginning with the first one available.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>active-backup</code></strong> or <strong class="userinput"><code>1</code></strong> — Sets an active-backup policy for fault tolerance. Transmissions are received and sent out via the first available bonded slave interface. Another bonded slave interface is only used if the active bonded slave interface fails.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-xor</code></strong> or <strong class="userinput"><code>2</code></strong> — Transmissions are based on the selected hash policy. The default is to derive a hash by XOR of the source and destination MAC addresses multiplied by the modulo of the number of slave interfaces. In this mode traffic destined for specific peers will always be sent over the same interface. As the destination is determined by the MAC addresses this method works best for traffic to peers on the same link or local network. If traffic has to pass through a single router then this mode of traffic balancing will be suboptimal.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>broadcast</code></strong> or <strong class="userinput"><code>3</code></strong> — Sets a broadcast policy for fault tolerance. All transmissions are sent on all slave interfaces.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>802.3ad</code></strong> or <strong class="userinput"><code>4</code></strong> — Sets an IEEE 802.3ad dynamic link aggregation policy. Creates aggregation groups that share the same speed and duplex settings. Transmits and receives on all slaves in the active aggregator. Requires a switch that is 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-tlb</code></strong> or <strong class="userinput"><code>5</code></strong> — Sets a Transmit Load Balancing (TLB) policy for fault tolerance and load balancing. The outgoing traffic is distributed according to the current load on each slave interface. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed slave. This mode is only suitable for local addresses known to the kernel bonding module and therefore cannot be used behind a bridge with virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-alb</code></strong> or <strong class="userinput"><code>6</code></strong> — Sets an Adaptive Load Balancing (ALB) policy for fault tolerance and load balancing. Includes transmit and receive load balancing for <code class="systemitem">IPv4</code> traffic. Receive load balancing is achieved through <code class="systemitem">ARP</code> negotiation. This mode is only suitable for local addresses known to the kernel bonding module and therefore cannot be used behind a bridge with virtual machines.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">primary=<em class="replaceable"><code>interface_name</code></em> </code> </span></dt><dd><div class="para">
+ Specifies the interface name, such as <strong class="userinput"><code>eth0</code></strong>, of the primary device. The <code class="literal">primary</code> device is the first of the bonding interfaces to be used and is not abandoned unless it fails. This setting is particularly useful when one NIC in the bonding interface is faster and, therefore, able to handle a bigger load.
+ </div><div class="para">
+ This setting is only valid when the bonding interface is in <strong class="userinput"><code>active-backup</code></strong> mode. See <a href="https://www.kernel.org/doc/Documentation/networking/bonding.txt">https://www.kernel.org/doc/Documentation/networking/bonding.txt</a> for more information.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">primary_reselect=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Specifies the reselection policy for the primary slave. This affects how the primary slave is chosen to become the active slave when failure of the active slave or recovery of the primary slave occurs. This parameter is designed to prevent flip-flopping between the primary slave and other slaves. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>always</code></strong> or <strong class="userinput"><code>0</code></strong> (default) — The primary slave becomes the active slave whenever it comes back up.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>better</code></strong> or <strong class="userinput"><code>1</code></strong> — The primary slave becomes the active slave when it comes back up, if the speed and duplex of the primary slave is better than the speed and duplex of the current active slave.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>failure</code></strong> or <strong class="userinput"><code>2</code></strong> — The primary slave becomes the active slave only if the current active slave fails and the primary slave is up.
+ </div></li></ul></div><div class="para">
+ The <code class="literal">primary_reselect</code> setting is ignored in two cases:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If no slaves are active, the first slave to recover is made the active slave.
+ </div></li><li class="listitem"><div class="para">
+ When initially enslaved, the primary slave is always made the active slave.
+ </div></li></ul></div><div class="para">
+ Changing the <code class="literal">primary_reselect</code> policy via <code class="systemitem">sysfs</code> will cause an immediate selection of the best active slave according to the new policy. This may or may not result in a change of the active slave, depending upon the circumstances
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">resend_igmp=<em class="replaceable"><code>range</code></em></code></span></dt><dd><div class="para">
+ Specifies the number of IGMP membership reports to be issued after a failover event. One membership report is issued immediately after the failover, subsequent packets are sent in each 200ms interval.
+ </div><div class="para">
+ The valid range is <code class="literal">0</code> to <code class="literal">255</code>; the default value is <code class="literal">1</code>. A value of <code class="literal">0</code> prevents the IGMP membership report from being issued in response to the failover event.
+ </div><div class="para">
+ This option is useful for bonding modes <code class="command">balance-rr</code> (mode 0), <code class="command">active-backup</code> (mode 1), <code class="command">balance-tlb</code> (mode 5) and <code class="command">balance-alb</code> (mode 6), in which a failover can switch the IGMP traffic from one slave to another. Therefore a fresh IGMP report must be issued to cause the switch to forward the incoming IGMP traffic over the newly selected slave.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">updelay=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how long to wait before enabling a link. The value must be a multiple of the value specified in the <code class="literal">miimon</code> parameter. The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">use_carrier=<em class="replaceable"><code>number</code></em> </code> </span></dt><dd><div class="para">
+ Specifies whether or not <code class="literal">miimon</code> should use MII/ETHTOOL ioctls or <code class="function">netif_carrier_ok()</code> to determine the link state. The <code class="function">netif_carrier_ok()</code> function relies on the device driver to maintains its state with <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em></code>; most device drivers support this function.
+ </div><div class="para">
+ The MII/ETHTOOL ioctls tools utilize a deprecated calling sequence within the kernel. However, this is still configurable in case your device driver does not support <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em></code>.
+ </div><div class="para">
+ Valid values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> — Default setting. Enables the use of <code class="function">netif_carrier_ok()</code>.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> — Enables the use of MII/ETHTOOL ioctls.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If the bonding interface insists that the link is up when it should not be, it is possible that your network device driver does not support <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em></code>.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">xmit_hash_policy=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Selects the transmit hash policy used for slave selection in <strong class="userinput"><code>balance-xor</code></strong> and <strong class="userinput"><code>802.3ad</code></strong> modes. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> or <strong class="userinput"><code>layer2</code></strong> — Default setting. This parameter uses the XOR of hardware MAC addresses to generate the hash. The formula used is:
+ </div><pre class="screen">(<em class="replaceable"><code>source_MAC_address</code></em> XOR <em class="replaceable"><code>destination_MAC</code></em>) MODULO <em class="replaceable"><code>slave_count</code></em>
+</pre><div class="para">
+ This algorithm will place all traffic to a particular network peer on the same slave, and is 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> or <strong class="userinput"><code>layer3+4</code></strong> — Uses upper layer protocol information (when available) to generate the hash. This allows for traffic to a particular network peer to span multiple slaves, although a single connection will not span multiple slaves.
+ </div><div class="para">
+ The formula for unfragmented TCP and UDP packets used is:
+ </div><pre class="screen">((<em class="replaceable"><code>source_port</code></em> XOR <em class="replaceable"><code>dest_port</code></em>) XOR
+ ((<em class="replaceable"><code>source_IP</code></em> XOR <em class="replaceable"><code>dest_IP</code></em>) AND <code class="constant">0xffff</code>)
+ MODULO <em class="replaceable"><code>slave_count</code></em>
+</pre><div class="para">
+ For fragmented TCP or UDP packets and all other <code class="systemitem">IP</code> protocol traffic, the source and destination port information is omitted. For non-<code class="systemitem">IP</code> traffic, the formula is the same as the <code class="command">layer2</code> transmit hash policy.
+ </div><div class="para">
+ This policy intends to mimic the behavior of certain switches; particularly, Cisco switches with PFC2 as well as some Foundry and IBM products.
+ </div><div class="para">
+ The algorithm used by this policy is not 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>2</code></strong> or <strong class="userinput"><code>layer2+3</code></strong> — Uses a combination of layer2 and layer3 protocol information to generate the hash.
+ </div><div class="para">
+ Uses XOR of hardware MAC addresses and <code class="systemitem">IP</code> addresses to generate the hash. The formula is:
+ </div><pre class="screen">(((<em class="replaceable"><code>source_IP</code></em> XOR <em class="replaceable"><code>dest_IP</code></em>) AND <code class="constant">0xffff</code>) XOR
+ ( <em class="replaceable"><code>source_MAC</code></em> XOR <em class="replaceable"><code>destination_MAC</code></em> ))
+ MODULO <em class="replaceable"><code>slave_count</code></em>
+</pre><div class="para">
+ This algorithm will place all traffic to a particular network peer on the same slave. For non-<code class="systemitem">IP</code> traffic, the formula is the same as for the layer2 transmit hash policy.
+ </div><div class="para">
+ This policy is intended to provide a more balanced distribution of traffic than layer2 alone, especially in environments where a layer3 gateway device is required to reach most destinations.
+ </div><div class="para">
+ This algorithm is 802.3ad compliant.
+ </div></li></ul></div></dd></dl></div></div></div><div class="section" id="sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.5. Using the NetworkManager Command Line Tool, nmcli</h2></div></div></div><div class="para">
+ To create a bond, named <em class="replaceable"><code>mybond0</code></em>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type bond con-name <em class="replaceable"><code>mybond0</code></em> ifname <em class="replaceable"><code>mybond0</code></em> mode active-backup</code>
+Connection 'mybond0' (9301ff97-abbc-4432-aad1-246d7faea7fb) successfully added.</pre>
+ To add a slave interface, issue a command in the following form:
+<pre class="screen">~]$ <code class="command">nmcli con add type bond-slave ifname <em class="replaceable"><code>ens7</code></em> master <em class="replaceable"><code>mybond0</code></em></code></pre>
+ To add additional slaves, repeat the previous command with a new interface, for example:
+<pre class="screen">~]$ <code class="command">nmcli con add type bond-slave ifname <em class="replaceable"><code>ens3</code></em> master <em class="replaceable"><code>mybond0</code></em></code>
+Connection 'bond-slave-ens3-1' (50c59350-1531-45f4-ba04-33431c16e386) successfully added.</pre>
+ Note that as no <code class="command">con-name</code> was given for the slaves, the name was derived from the interface name by prepending the type. At time of writing, <span class="application"><strong>nmcli</strong></span> only supports Ethernet slaves.
+ </div><div class="para">
+ In order to bring up a bond, the slaves must be brought up first as follows:
+<pre class="screen">~]$ <code class="command">nmcli con up bond-slave-<em class="replaceable"><code>ens7</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/14)</pre>
+
+<pre class="screen">~]$ <code class="command">nmcli con up bond-slave-<em class="replaceable"><code>ens3</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/15)</pre>
+ Now bring up the bond as follows:
+<pre class="screen">~]$ <code class="command">nmcli con up bond-<em class="replaceable"><code>mybond0</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/16)</pre>
+
+ </div><div class="para">
+ See <a class="xref" href="#sec-Using_the_NetworkManager_Command_Line_Tool_nmcli">Section 2.4, “Using the NetworkManager Command Line Tool, nmcli”</a> for an introduction to <span class="application"><strong>nmcli</strong></span>
+ </div></div><div class="section" id="sec-Configure_Network_Bonding-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.6. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding network bonding.
+ </div><div class="section" id="sec-Configure_Network_Bonding-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.6.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">nmcli(1)</code> man page — Describes <span class="application"><strong>NetworkManager</strong></span>'s command‐line tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nmcli-examples(5)</code> man page — Gives examples of <span class="application"><strong>nmcli</strong></span> commands.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nm-settings(5)</code> man page — Description of settings and parameters of <span class="application"><strong>NetworkManager</strong></span> connections.
+ </div></li></ul></div></div><div class="section" id="sec-Configure_Network_Bonding_Online_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.6.2. Online Documentation</h3></div></div></div><div class="para">
+ <div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><em class="citetitle">Fedora 20 System Administrator's Guide</em></span></dt><dd><div class="para">
+ Explains the use of kernel module capabilities.
+ </div></dd></dl></div>
+ </div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-Configure_Network_Teaming" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 5. Configure Network Teaming</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sec-Understanding_Network_Teaming">5.1. Understanding Network Teaming</a></span></dt><dt><span class="section"><a href="#sec-Comparison_of_Network_Teaming_to_Bonding">5.2. Comparison of Network Teaming to Bonding</a></span></dt><dt><span class="section"><a href="#sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces">5.3. Understanding the Default Behavior of Master and Slave Interfaces</a></span></dt><dt><span class="section"><a href="#sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners">5.4. Understanding the Network Teaming Daemon and the "Runners"</a></span></dt><dt><span class="section"><a href="#sec-Install_the_Network_Teaming_Daemon">5.5. Install the
Network Teaming Daemon</a></span></dt><dt><span class="section"><a href="#sec-Converting_a_Bond_to_a_Team">5.6. Converting a Bond to a Team</a></span></dt><dt><span class="section"><a href="#sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team">5.7. Selecting Interfaces to Use as Ports for a Network Team</a></span></dt><dt><span class="section"><a href="#sec-Selecting_Network_Team_Configuration_Methods">5.8. Selecting Network Team Configuration Methods</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Network_Team_Using_a_GUI">5.9. Creating a Network Team Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_Team_Connection">5.9.1. Establishing a Team Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_a_Network_Team_Using-the_Command_Line">5.10. Configure a Network Team Using the Command Line</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Creating_a_Network_Team_Using
_teamd">5.10.1. Creating a Network Team Using teamd</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Network_Team_Using_ifcfg_Files">5.10.2. Creating a Network Team Using ifcfg Files</a></span></dt><dt><span class="section"><a href="#sec-Add_a_port_to_a_Network_Team_Using_iputils">5.10.3. Add a Port to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="#sec-Listing_the_ports_of_a_Team_Using_teamnl">5.10.4. Listing the ports of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Options_of_a_Team_Using_teamnl">5.10.5. Configuring Options of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="#sec-Add_an_address_to_a_Network_Team_Using_iputils">5.10.6. Add an Address to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="#sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils">5.10.7. Bring up an Interface to a Network Team Using iputils</a></span></d
t><dt><span class="section"><a href="#sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl">5.10.8. Viewing the Active Port Options of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="#sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl">5.10.9. Setting the Active Port Options of a Team Using teamnl</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Controlling_teamd_with_teamdctl">5.11. Controlling teamd with teamdctl</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Add_a_port_to_a_Network_Team">5.11.1. Add a Port to a Network Team</a></span></dt><dt><span class="section"><a href="#sec-Remove_a_Port_From_a_Network_Team">5.11.2. Remove a Port From a Network Team</a></span></dt><dt><span class="section"><a href="#sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team">5.11.3. Apply a Configuration to a Port in a Network Team</a></span></dt><dt><span class="section"><a href="#sec-View_the_Configuration_of_a_Port_in_a_Network_Team"
>5.11.4. View the Configuration of a Port in a Network Team</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_teamd_Runners">5.12. Configure teamd Runners</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configure_the_broadcast_Runner">5.12.1. Configure the broadcast Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_the_random_Runner">5.12.2. Configure the random Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_the_roundrobin_Runner">5.12.3. Configure the roundrobin Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_the_activebackup_Runner">5.12.4. Configure the activebackup Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_the_loadbalance_Runner">5.12.5. Configure the loadbalance Runner</a></span></dt><dt><span class="section"><a href="#sec-Configure_the_LACP_Runner">5.12.6. Configure the LACP (802.3ad) Runner</a></span></dt><dt><span class="section
"><a href="#sec-Configure_Monitoring_of_the_Link_State">5.12.7. Configure Monitoring of the Link State</a></span></dt><dt><span class="section"><a href="#sec-Configure_Port_Selection_Override">5.12.8. Configure Port Selection Override</a></span></dt><dt><span class="section"><a href="#sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm">5.12.9. Configure BPF-based Tx Port Selectors</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_Network_Teaming_Using_nmcli">5.13. Configure Network Teaming Using nmcli</a></span></dt><dt><span class="section"><a href="#sec-Network_Teaming-additional_resources">5.14. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-teamd-docs-inst">5.14.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-teamd_docs-online">5.14.2. Online Documentation</a></span></dt></dl></dd></dl></div><div class="section" id="sec-Understanding_Network_Teaming"><div
class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. Understanding Network Teaming</h2></div></div></div><div class="para">
+ The combining or aggregating together of network links in order to provide a logical link with higher throughput, or to provide redundancy, is known by many names such as <span class="quote">“<span class="quote">channel bonding</span>”</span>, <span class="quote">“<span class="quote">Ethernet bonding</span>”</span>, <span class="quote">“<span class="quote">port trunking</span>”</span>, <span class="quote">“<span class="quote">channel teaming</span>”</span>, <span class="quote">“<span class="quote">NIC teaming</span>”</span>, <span class="quote">“<span class="quote">link aggregation</span>”</span>, and so on. This concept as originally implemented in the Linux kernel is widely referred to as <span class="quote">“<span class="quote">bonding</span>”</span>. The term Network Teaming has been chosen to refer to this new implementation of the concept. The existing bonding driver is unaffected, Network Teaming is offered as an alternative and does not
replace bonding in Fedora.
+ </div><div class="para">
+ Network Teaming, or Team, is designed to implement the concept in a different way by providing a small kernel driver to implement the fast handling of packet flows, and various user-space applications to do everything else in user space. The driver has an <em class="firstterm">Application Programming Interface</em> (<acronym class="acronym">API</acronym>), referred to as <span class="quote">“<span class="quote">Team Netlink API</span>”</span>, which implements Netlink communications. User-space applications can use this API to communicate with the driver. A library, referred to as <span class="quote">“<span class="quote">lib</span>”</span>, has been provided to do user space wrapping of Team Netlink communications and RT Netlink messages. An application daemon, <code class="systemitem">teamd</code>, which uses Libteam lib is also provided. One instance of <code class="systemitem">teamd</code> can control one instance of the Team driver. The daemon implements the l
oad-balancing and active-backup logic, such as round-robin, by using additional code referred to as <span class="quote">“<span class="quote">runners</span>”</span>. By separating the code in this way, the Network Teaming implementation presents an easily extensible and scalable solution for load-balancing and redundancy requirements. For example, custom runners can be relatively easily written to implement new logic via <code class="systemitem">teamd</code>, and even <code class="systemitem">teamd</code> is optional, users can write their own application to use <span class="application"><strong>libteam</strong></span>.
+ </div><div class="para">
+ A tool to control a running instance of <code class="systemitem">teamd</code> using D-bus is provided by <span class="application"><strong>teamdctl</strong></span>. It provides a D-Bus wrapper around the <code class="systemitem">teamd</code> D-Bus API. By default, <code class="systemitem">teamd</code> listens and communicates using Unix Domain Sockets but still monitors D-Bus. This is to ensure that <code class="systemitem">teamd</code> can be used in environments where D-Bus is not present or not yet loaded. For example, when booting over <code class="systemitem">teamd</code> links D-Bus would not yet be loaded. The <span class="application"><strong>teamdctl</strong></span> tool can be used during run time to read the configuration, the state of link-watchers, check and change the state of ports, add and remove ports, and to change ports between active and backup states.
+ </div><div class="para">
+ Team Netlink API communicates with user-space applications using Netlink messages. The user-space library <span class="application"><strong>libteam</strong></span> does not directly interact with the API, but uses <span class="application"><strong>libnl</strong></span> or <span class="application"><strong>teamnl</strong></span> to interact with the driver API.
+ </div><div class="para">
+ To sum up, the instances of Team driver, running in the kernel, do not get configured or controlled directly. All configuration is done with the aid of user space applications, such as the <span class="application"><strong>teamd</strong></span> application. The application then directs the kernel driver part accordingly.
+ </div></div><div class="section" id="sec-Comparison_of_Network_Teaming_to_Bonding"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. Comparison of Network Teaming to Bonding</h2></div></div></div><div class="table" id="Bonding_Teaming_Comparison"><h6>Table 5.1. A Comparison of Features in Bonding and Team</h6><div class="table-contents"><table summary="A Comparison of Features in Bonding and Team" border="1"><colgroup><col align="left" class="c1" width="33%" /><col align="left" class="c2" width="33%" /><col align="left" class="c3" width="33%" /></colgroup><thead><tr><th class="" align="left">
+ Feature
+ </th><th class="" align="left">
+ Bonding
+ </th><th class="" align="left">
+ Team
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ broadcast Tx policy
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ round-robin Tx policy
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ active-backup Tx policy
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ LACP (802.3ad) support
+ </td><td class="" align="left">
+ Yes (passive only)
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ Hash-based Tx policy
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ User can set hash function
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ Tx load-balancing support (TLB)
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ LACP hash port select
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ load-balancing for LACP support
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ Ethtool link monitoring
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ ARP link monitoring
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ NS/NA (IPv6) link monitoring
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ ports up/down delays
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ port priorities and stickiness (<span class="quote">“<span class="quote">primary</span>”</span> option enhancement)
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ separate per-port link monitoring setup
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ multiple link monitoring setup
+ </td><td class="" align="left">
+ Limited
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ lockless Tx/Rx path
+ </td><td class="" align="left">
+ No (rwlock)
+ </td><td class="" align="left">
+ Yes (RCU)
+ </td></tr><tr><td class="" align="left">
+ VLAN support
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ user-space runtime control
+ </td><td class="" align="left">
+ Limited
+ </td><td class="" align="left">
+ Full
+ </td></tr><tr><td class="" align="left">
+ Logic in user-space
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ Extensibility
+ </td><td class="" align="left">
+ Hard
+ </td><td class="" align="left">
+ Easy
+ </td></tr><tr><td class="" align="left">
+ Modular design
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ Performance overhead
+ </td><td class="" align="left">
+ Low
+ </td><td class="" align="left">
+ Very Low
+ </td></tr><tr><td class="" align="left">
+ D-Bus interface
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ multiple device stacking
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ zero config using LLDP
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ (in planning)
+ </td></tr><tr><td class="" align="left">
+ NetworkManager support
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.3. Understanding the Default Behavior of Master and Slave Interfaces</h2></div></div></div><div class="para">
+ When controlling teamed port interfaces using the <code class="systemitem">NetworkManager</code> daemon, and especially when fault finding, keep the following in mind:
+ <div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Starting the master interface does not automatically start the port interfaces.
+ </div></li><li class="listitem"><div class="para">
+ Starting a port interface always starts the master interface.
+ </div></li><li class="listitem"><div class="para">
+ Stopping the master interface also stops the port interfaces.
+ </div></li><li class="listitem"><div class="para">
+ A master without ports can start static <code class="systemitem">IP</code> connections.
+ </div></li><li class="listitem"><div class="para">
+ A master without ports waits for ports when starting <code class="systemitem">DHCP</code> connections.
+ </div></li><li class="listitem"><div class="para">
+ A master with a <code class="systemitem">DHCP</code> connection waiting for ports completes when a port with a carrier is added.
+ </div></li><li class="listitem"><div class="para">
+ A master with a <code class="systemitem">DHCP</code> connection waiting for ports continues waiting when a port without a carrier is added.
+ </div></li></ol></div>
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The use of direct cable connections without network switches is not supported for teaming. The failover mechanisms described here will not work as expected without the presence of network switches.
+ </div></div></div></div><div class="section" id="sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.4. Understanding the Network Teaming Daemon and the "Runners"</h2></div></div></div><div class="para">
+ The Team daemon, <code class="systemitem">teamd</code>, uses <span class="application"><strong>libteam</strong></span> to control one instance of the team driver. This instance of the team driver adds instances of a hardware device driver to form a <span class="quote">“<span class="quote">team</span>”</span> of network links. The team driver presents a network interface, <span class="interface">team0</span> for example, to the other parts of the kernel. The interfaces created by instances of the team driver are given names such as <span class="interface">team0</span>, <span class="interface">team1</span>, and so forth in the documentation. This is for ease of understanding and other names can be used. The logic common to all methods of teaming is implemented by <code class="systemitem">teamd</code>; those functions that are unique to the different load sharing and backup methods, such as round-robin, are implemented by separate units of code referred to as <span class
="quote">“<span class="quote">runners</span>”</span>. Because words such as <span class="quote">“<span class="quote">module</span>”</span> and <span class="quote">“<span class="quote">mode</span>”</span> already have specific meanings in relation to the kernel, the word <span class="quote">“<span class="quote">runner</span>”</span> was chosen to refer to these units of code. The user specifies the runner in the JSON format configuration file and the code is then compiled into an instance of <code class="systemitem">teamd</code> when the instance is created. A runner is not a plug-in because the code for a runner is compiled into an instance of <code class="systemitem">teamd</code> as it is being created. Code could be created as a plug-in for <code class="systemitem">teamd</code> should the need arise.
+ </div><div class="para">
+ The following runners are available at time of writing.
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ broadcast (data is transmitted over all ports)
+ </div></li><li class="listitem"><div class="para">
+ round-robin (data is transmitted over all ports in turn)
+ </div></li><li class="listitem"><div class="para">
+ active-backup (one port or link is used while others are kept as a backup)
+ </div></li><li class="listitem"><div class="para">
+ loadbalance (with active Tx load balancing and BPF-based Tx port selectors)
+ </div></li><li class="listitem"><div class="para">
+ lacp (implements the 802.3ad Link Aggregation Control Protocol)
+ </div></li></ul></div>
+
+ </div><div class="para">
+ In addition, the following link-watchers are available:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>ethtool</strong></span> (Libteam lib uses <span class="application"><strong>ethtool</strong></span> to watch for link state changes). This is the default if no other link-watcher is specified in the configuration file.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>arp_ping</strong></span> (The <span class="application"><strong>arp_ping</strong></span> utility is used to monitor the presence of a far-end hardware address using ARP packets.)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>nsna_ping</strong></span> (Neighbor Advertisements and Neighbor Solicitation from the <code class="systemitem">IPv6</code> Neighbor Discovery protocol are used to monitor the presence of a neighbor's interface)
+ </div></li></ul></div>
+ There are no restrictions in the code to prevent a particular link-watcher from being used with a particular runner, however when using the <span class="application"><strong>lacp</strong></span> runner, <span class="application"><strong>ethtool</strong></span> is the only recommended link-watcher.
+ </div></div><div class="section" id="sec-Install_the_Network_Teaming_Daemon"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.5. Install the Network Teaming Daemon</h2></div></div></div><div class="para">
+ The networking teaming daemon, <code class="systemitem">teamd</code>, is not installed by default. To install <code class="systemitem">teamd</code>, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">yum install teamd</code></pre>
+
+ </div></div><div class="section" id="sec-Converting_a_Bond_to_a_Team"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.6. Converting a Bond to a Team</h2></div></div></div><div class="para">
+ It is possible to convert existing bonding configuration files to team configuration files using the <span class="application"><strong>bond2team</strong></span> tool. It can convert bond configuration files in <code class="filename">ifcfg</code> format to team configuration files in either <code class="filename">ifcfg</code> or JSON format. Note that firewall rules, alias interfaces, and anything that might be tied to the original interface name can break after the renaming because the tool will only change the <code class="filename">ifcfg</code> file, nothing else.
+ </div><div class="para">
+ To see some examples of the command format, issue the following command:
+<pre class="screen">~]$ <code class="command">bond2team --examples</code></pre>
+ New files will be created in a directory whose name starts with <code class="filename">/tmp/bond2team.XXXXXX/</code>, where XXXXXX is a random string. After creating the new configuration files, move the old bonding files to a backup folder and then move the new files to the <code class="filename">/etc/sysconfig/network-scripts/</code> directory.
+ </div><div class="example" id="ex-Convert_a_Bond_to_a_Team"><h6>Example 5.1. Convert a Bond to a Team</h6><div class="example-contents"><div class="para">
+ To convert a current <code class="literal">bond0</code> configuration to team <code class="literal">ifcfg</code>, issue a command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">/usr/bin/bond2team --master bond0</code></pre>
+ Note that this will retain the name <code class="literal">bond0</code>. To use a new name to save the configuration, use the <code class="option">--rename</code> as follows:
+<pre class="screen">~]# <code class="command">/usr/bin/bond2team --master bond0 --rename team0</code></pre>
+ add the <code class="option">--json</code> option to output JSON format files instead of <code class="literal">ifcfg</code> files. See the <code class="filename">teamd.conf(5)</code> man page for examples of JSON format.
+ </div></div></div><br class="example-break" /><div class="example" id="ex_Convert_a_Bond_to_a_Team_and_Specify_the_File_Path"><h6>Example 5.2. Convert a Bond to a Team and Specify the File Path</h6><div class="example-contents"><div class="para">
+ To convert a current <code class="literal">bond0</code> configuration to team <code class="literal">ifcfg</code>, and to manually specify the path to the <code class="literal">ifcfg</code> file, issue a command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">/usr/bin/bond2team --master bond0 --configdir <em class="replaceable"><code>/path/to/ifcfg-file</code></em></code></pre>
+ add the <code class="option">--json</code> option to output JSON format files instead of <code class="literal">ifcfg</code> files.
+ </div></div></div><br class="example-break" /><div class="example" id="ex_Create_a_Team_Configuration_Using_Bond2team"><h6>Example 5.3. Create a Team Configuration Using Bond2team</h6><div class="example-contents"><div class="para">
+ It is also possible to create a team configuration by supplying the <span class="application"><strong>bond2team</strong></span> tool with a list of bonding parameters. For example:
+<pre class="screen">~]# <code class="command">/usr/bin/bond2team --bonding_opts "mode=1 miimon=500"</code></pre>
+ Ports can also be supplied on the command line as follows:
+<pre class="screen">~]# <code class="command">/usr/bin/bond2team --bonding_opts "mode=1 miimon=500 primary=eth1 \</code>
+ <code class="command">primary_reselect-0" --port eth1 --port eth2 --port eth3 --port eth4</code></pre>
+
+ </div></div></div><br class="example-break" /><div class="para">
+ See the <code class="filename">bond2team(1)</code> man page for further details. For an explanation of bonding parameters, see <a class="xref" href="#sec-Using_Channel_Bonding">Section 4.4, “Using Channel Bonding”</a>
+ </div></div><div class="section" id="sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.7. Selecting Interfaces to Use as Ports for a Network Team</h2></div></div></div><div class="para">
+ To view the available interfaces, issue the following command:
+<pre class="screen">~]$ <code class="command">ip link show</code>
+1: lo: <LOOPBACK,UP,LOWER_UP > mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP > mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
+ link/ether 52:54:00:6a:02:8a brd ff:ff:ff:ff:ff:ff
+3: em2: <BROADCAST,MULTICAST,UP,LOWER_UP > mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
+link/ether 52:54:00:9b:6d:2a brd ff:ff:ff:ff:ff:ff</pre>
+ From the available interfaces, determine which are suitable for adding to your network team and then proceed to <a class="xref" href="#sec-Selecting_Network_Team_Configuration_Methods">Section 5.8, “Selecting Network Team Configuration Methods”</a>
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The Team developers prefer the term <span class="quote">“<span class="quote">port</span>”</span> rather than <span class="quote">“<span class="quote">slave</span>”</span>, however <span class="application"><strong>NetworkManager</strong></span> uses the term <span class="quote">“<span class="quote">team-slave</span>”</span> to refer to interfaces that make up a team.
+ </div></div></div></div><div class="section" id="sec-Selecting_Network_Team_Configuration_Methods"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.8. Selecting Network Team Configuration Methods</h2></div></div></div><div class="para">
+ <span class="bold bold"><strong>To configure a network team using a graphical user interface</strong></span>, see <a class="xref" href="#sec-Creating_a_Network_Team_Using_a_GUI">Section 5.9, “Creating a Network Team Using a GUI”</a>
+ </div><div class="para">
+ <span class="bold bold"><strong>To create a network team using the Team daemon</strong></span>, <code class="systemitem">teamd</code>, proceed to <a class="xref" href="#sec-Creating_a_Network_Team_Using_teamd">Section 5.10.1, “Creating a Network Team Using teamd”</a>.
+ </div><div class="para">
+ <span class="bold bold"><strong>To create a network team using configuration files</strong></span>, proceed to <a class="xref" href="#sec-Creating_a_Network_Team_Using_ifcfg_Files">Section 5.10.2, “Creating a Network Team Using ifcfg Files”</a>.
+ </div><div class="para">
+ <span class="bold bold"><strong>To create a network team using the command-line tool</strong></span>, <span class="application"><strong>nmcli</strong></span>, proceed to <a class="xref" href="#sec-Configure_Network_Teaming_Using_nmcli">Section 5.13, “Configure Network Teaming Using nmcli”</a>.
+ </div></div><div class="section" id="sec-Creating_a_Network_Team_Using_a_GUI"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.9. Creating a Network Team Using a GUI</h2></div></div></div><div class="section" id="sec-Establishing_a_Team_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.1. Establishing a Team Connection</h3></div></div></div><div class="para">
+ You can use the GNOME <span class="application"><strong>control-center</strong></span> utility to direct <span class="application"><strong>NetworkManager</strong></span> to create a team from two or more Wired or InfiniBand connections. It is not necessary to create the connections to be teamed first. They can be configured as part of the process to configure the team. You must have the MAC addresses of the interfaces available in order to complete the configuration process.
+ </div><div class="procedure" id="procedure-Adding_a_New_Team_Connection"><h6>Procedure 5.1. Adding a New Team Connection</h6><div class="para">
+ You can configure a team connection by opening the <span class="guilabel"><strong>Network</strong></span> window, clicking the plus symbol, and selecting <span class="guilabel"><strong>Team</strong></span> from the list.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Click the plus symbol to open the selection list. Select <span class="guilabel"><strong>Team</strong></span>. The <span class="guilabel"><strong>Editing Team Connection <em class="replaceable"><code>1</code></em></strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ On the <span class="guilabel"><strong>Team</strong></span> tab, click <span class="guibutton"><strong>Add</strong></span> and select the type of interface you want to use with the team connection. Click the <span class="guibutton"><strong>Create</strong></span> button. Note that the dialog to select the port type only comes up when you create the first port; after that, it will automatically use that same type for all further ports.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Editing team0 port 1</strong></span> window appears. Fill in the MAC address of the first interface to be added to the team.
+ </div></li><li class="step"><div class="para">
+ If custom port settings are to be applied, click on the <span class="guilabel"><strong>Team Port</strong></span> tab and enter a JSON configuration string or import it from a file.
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guibutton"><strong>Save</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ The name of the teamed port appears in the <span class="guilabel"><strong>Teamed connections</strong></span> window. Click the <span class="guibutton"><strong>Add</strong></span> button to add further port connections.
+ </div></li><li class="step"><div class="para">
+ Review and confirm the settings and then click the <span class="guilabel"><strong>Save</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Edit the team-specific settings by referring to <a class="xref" href="#sec-Configuring_the_Team_Tab">Section 5.9.1.1, “Configuring the Team Tab”</a> below.
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_Team_Connection"><h6>Procedure 5.2. Editing an Existing Team Connection</h6><div class="para">
+ Follow these steps to edit an existing bond connection.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the connection you want to edit and click the <span class="guilabel"><strong>Options</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>General</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Configure the connection name, auto-connect behavior, and availability settings.
+ </div><div class="para">
+ Five settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types, see the <span class="guilabel"><strong>General</strong></span> tab:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the menu of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to this network when it is available</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="#sec-Connecting_to_a_Network_Automatically">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>All users may connect to this network</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="#sec-System-wide_and_Private_Connection_Profiles">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to VPN when using this connection</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to a VPN connection when it is available. Select the VPN from the drop-down menu.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Firewall Zone</strong></span> — Select the firewall zone from the drop-down menu.
+ </div></li></ul></div></li><li class="step"><div class="para">
+ Edit the team-specific settings by referring to <a class="xref" href="#sec-Configuring_the_Team_Tab">Section 5.9.1.1, “Configuring the Team Tab”</a> below.
+ </div></li></ol></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-team">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your team connection, click the <span class="guibutton"><strong>Save</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network</strong></span> window and clicking <span class="guilabel"><strong>Options</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ IPv6 settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv6_Settings">Section 2.2.10.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div><div class="section" id="sec-Configuring_the_Team_Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">5.9.1.1. Configuring the Team Tab</h4></div></div></div><div class="para">
+ If you have already added a new team connection you can enter a custom JSON configuration string in the text box or import a configuration file. Click <span class="guilabel"><strong>Save</strong></span> to apply the JSON configuration to the team interface.
+ </div><div class="para">
+ For examples of JSON strings, see <a class="xref" href="#sec-Configure_teamd_Runners">Section 5.12, “Configure teamd Runners”</a>
+ </div><div class="para">
+ See <a class="xref" href="#procedure-Adding_a_New_Team_Connection">Procedure 5.1, “Adding a New Team Connection”</a> for instructions on how to add a new team.
+ </div></div></div></div><div class="section" id="sec-Configure_a_Network_Team_Using-the_Command_Line"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.10. Configure a Network Team Using the Command Line</h2></div></div></div><div class="section" id="sec-Creating_a_Network_Team_Using_teamd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.1. Creating a Network Team Using teamd</h3></div></div></div><div class="para">
+ To create a network team, a JSON format configuration file is required for the virtual interface that will serve as the interface to the team of ports or links. A quick way is to copy the example configuration files and then edit them using an editor running with <code class="systemitem">root</code> privileges. To list the available example configurations, enter the following command:
+<pre class="screen">~]$ <code class="command">ls /usr/share/doc/teamd-*/example_configs/</code>
+activebackup_arp_ping_1.conf activebackup_multi_lw_1.conf loadbalance_2.conf
+activebackup_arp_ping_2.conf activebackup_nsna_ping_1.conf loadbalance_3.conf
+activebackup_ethtool_1.conf broadcast.conf random.conf
+activebackup_ethtool_2.conf lacp_1.conf roundrobin_2.conf
+activebackup_ethtool_3.conf loadbalance_1.conf roundrobin.conf</pre>
+ To view one of the included files, such as <code class="filename">activebackup_ethtool_1.conf</code>, enter the following command:
+<pre class="screen">~]$ <code class="command">cat /usr/share/doc/teamd-*/example_configs/activebackup_ethtool_1.conf</code>
+{
+ "device": "team0",
+ "runner": {"name": "activebackup"},
+ "link_watch": {"name": "ethtool"},
+ "ports": {
+ "eth1": {
+ "prio": -10,
+ "sticky": true
+ },
+ "eth2": {
+ "prio": 100
+ }
+ }
+}</pre>
+ Create a working configurations directory to store <code class="systemitem">teamd</code> configuration files. For example, as normal user, enter a command with the following format:
+<pre class="screen">~]$ <code class="command">mkdir ~/<em class="replaceable"><code>teamd_working_configs</code></em></code></pre>
+ Copy the file you have chosen to your working directory and edit it as necessary. As an example, you could use a command with the following format:
+<pre class="screen">~]$ <code class="command">cp /usr/share/doc/teamd-*/example_configs/activebackup_ethtool_1.conf \ ~/<em class="replaceable"><code>teamd_working_configs</code></em>/activebackup_ethtool_1.conf</code></pre>
+ To edit the file to suit your environment, for example to change the interfaces to be used as ports for the network team, open the file for editing as follows:
+<pre class="screen">~]$ <code class="command">vi ~/<em class="replaceable"><code>teamd_working_configs</code></em>/activebackup_ethtool_1.conf</code></pre>
+ Make any necessary changes and save the file. See the <code class="filename">vi(1)</code> man page for help on using the <span class="application"><strong>vi</strong></span> editor or use your preferred editor.
+ </div><div class="para">
+ Note that it is essential that the interfaces to be used as ports within the team must not be active, that is to say, they must be <span class="quote">“<span class="quote">down</span>”</span>, when adding them into a team device. To check their status, issue the following command:
+<pre class="screen">~]$ <code class="command">ip link show</code>
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
+ link/ether 52:54:00:d5:f7:d4 brd ff:ff:ff:ff:ff:ff
+3: em2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
+ link/ether 52:54:00:d8:04:70 brd ff:ff:ff:ff:ff:ff</pre>
+ In this example we see that both the interfaces we plan to use are <span class="quote">“<span class="quote">UP</span>”</span>.
+ </div><div class="para">
+ To take down an interface, issue a command as <code class="systemitem">root</code> in the following format:
+<pre class="screen">~]# <code class="command">ip link set down em1</code></pre>
+ Repeat for each interface as necessary.
+ </div><div class="para">
+ To create a team interface based on the configuration file, as <code class="systemitem">root</code> user, change to the working configurations directory (<em class="replaceable"><code>teamd_working_configs</code></em> in this example):
+<pre class="screen">~]# <code class="command">cd /home/<em class="replaceable"><code>user</code></em><em class="replaceable"><code>teamd_working_configs</code></em></code></pre>
+ Then issue a command in the following format:
+<pre class="screen">~]# <code class="command">teamd -g -f activebackup_ethtool_1.conf -d</code>
+Using team device "team0".
+Using PID file "/var/run/teamd/team0.pid"
+Using config file "/home/<em class="replaceable"><code>user</code></em>/teamd_working_configs/activebackup_ethtool_1.conf"</pre>
+ The <code class="option">-g</code> option is for debug messages, <code class="option">-f</code> option is to specify the configuration file to load, and the <code class="option">-d</code> option is to make the process run as a daemon after startup. See the <code class="filename">teamd(8)</code> man page for other options.
+ </div><div class="para">
+ To check the status of the team, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamdctl team0 state</code>
+setup:
+ runner: activebackup
+ports:
+ em1
+ link watches:
+ link summary: up
+ instance[link_watch_0]:
+ name: ethtool
+ link: up
+ em2
+ link watches:
+ link summary: up
+ instance[link_watch_0]:
+ name: ethtool
+ link: up
+runner:
+ active port: em1</pre>
+ </div><div class="para">
+ To apply an address to the network team interface, <span class="interface">team0</span>, issue a command as <code class="systemitem">root</code> in the following format:
+<pre class="screen">~]# <code class="command">ip addr add 192.168.23.2/24 dev team0</code></pre>
+
+ </div><div class="para">
+ To check the IP address of a team interface, issue a command as follows:
+<pre class="screen">~]$ <code class="command">ip addr show team0</code>
+4: team0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
+ link/ether 16:38:57:60:20:6f brd ff:ff:ff:ff:ff:ff
+ inet 192.168.23.2/24 scope global team0
+ valid_lft forever preferred_lft forever
+ inet6 2620:52:0:221d:1438:57ff:fe60:206f/64 scope global dynamic
+ valid_lft 2591880sec preferred_lft 604680sec
+ inet6 fe80::1438:57ff:fe60:206f/64 scope link
+ valid_lft forever preferred_lft forever</pre>
+
+ </div><div class="para">
+ To activate the team interface, or to bring it <span class="quote">“<span class="quote">up</span>”</span>, issue a command as <code class="systemitem">root</code> in the following format:
+<pre class="screen">~]# <code class="command">ip link set dev team0 up</code></pre>
+ </div><div class="para">
+ To temporarily deactivate the team interface, or to take it <span class="quote">“<span class="quote">down</span>”</span>, issue a command as <code class="systemitem">root</code> in the following format:
+<pre class="screen">~]# <code class="command">ip link set dev team0 down</code></pre>
+ </div><div class="para">
+ To terminate, or kill, an instance of the team daemon, as <code class="systemitem">root</code> user, issue a command in the following format:
+<pre class="screen">~]# <code class="command">teamd -t team0 -k</code></pre>
+ The <code class="option">-k</code> option is to specify that the instance of the daemon associated with the device <span class="interface">team0</span> is to be killed. See the <code class="filename">teamd(8)</code> man page for other options.
+ </div><div class="para">
+ For help on command-line options for <code class="systemitem">teamd</code>, issue the following command:
+<pre class="screen">~]$ <code class="command">teamd -h</code></pre>
+ In addition, see the <code class="filename">teamd(8)</code> man page.
+ </div></div><div class="section" id="sec-Creating_a_Network_Team_Using_ifcfg_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.2. Creating a Network Team Using ifcfg Files</h3></div></div></div><div class="para">
+ To create a networking team using <code class="literal">ifcfg</code> files, create a file in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory as follows:
+<pre class="screen">DEVICE=team0
+DEVICETYPE=Team
+ONBOOT=yes
+BOOTPROTO=none
+IPADDR=192.168.11.1
+PREFIX=24
+TEAM_CONFIG='{"runner": {"name": "activebackup"}, "link_watch": {"name": "ethtool"}}'</pre>
+ This creates the interface to the team, in other words, this is the master.
+ </div><div class="para">
+ To create a port to be a member of <span class="interface">team0</span>, create one or more files in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory as follows:
+<pre class="screen">DEVICE=eth1
+HWADDR=D4:85:64:01:46:9E
+DEVICETYPE=TeamPort
+ONBOOT=yes
+TEAM_MASTER=team0
+TEAM_PORT_CONFIG='{"prio": 100}'</pre>
+ Add additional port interfaces similar to the above as required, changing the DEVICE and HWADDR field to match the ports (the network devices) being added. If port priority is not specified by <code class="literal">prio</code> it defaults to <code class="literal">0</code>; it accepts negative and positive values in the range <code class="literal">-32,767</code> to <code class="literal">+32,767</code>.
+ </div><div class="para">
+ Specifying the hardware or MAC address using the <code class="command">HWADDR</code> directive will influence the device naming procedure. This is explained in <a class="xref" href="#ch-Consistent_Network_Device_Naming">Chapter 8, <em>Consistent Network Device Naming</em></a>.
+ </div><div class="para">
+ To bring up the network team, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ifup team0</code></pre>
+ To view the network team, issue the following command:
+<pre class="screen">~]$ <code class="command">ip link show</code></pre>
+ </div></div><div class="section" id="sec-Add_a_port_to_a_Network_Team_Using_iputils"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.3. Add a Port to a Network Team Using iputils</h3></div></div></div><div class="para">
+ To add a port <span class="interface">em1</span> to a network team <span class="interface">team0</span>, using the <span class="application"><strong>ip</strong></span> utility, issue the following commands as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ip link set dev em1 down</code>
+~]# <code class="command">ip link set dev em1 master team0</code></pre>
+ Add additional ports as required. Team driver will bring ports up automatically.
+ </div></div><div class="section" id="sec-Listing_the_ports_of_a_Team_Using_teamnl"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.4. Listing the ports of a Team Using teamnl</h3></div></div></div><div class="para">
+ To view or list the ports in a network team, using the <span class="application"><strong>teamnl</strong></span> utility, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamnl team0 ports</code>
+em2: up 100 fullduplex
+em1: up 100 fullduplex</pre>
+
+ </div></div><div class="section" id="sec-Configuring_Options_of_a_Team_Using_teamnl"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.5. Configuring Options of a Team Using teamnl</h3></div></div></div><div class="para">
+ To view or list all currently available options, using the <span class="application"><strong>teamnl</strong></span> utility, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamnl team0 options</code></pre>
+ To configure a team to use active backup mode, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamnl team0 setoption mode activebackup</code></pre>
+
+ </div></div><div class="section" id="sec-Add_an_address_to_a_Network_Team_Using_iputils"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.6. Add an Address to a Network Team Using iputils</h3></div></div></div><div class="para">
+ To add an address to a team <span class="interface">team0</span>, using the <span class="application"><strong>ip</strong></span> utility, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ip addr add 192.168.252.2/24 dev team0</code></pre>
+
+ </div></div><div class="section" id="sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.7. Bring up an Interface to a Network Team Using iputils</h3></div></div></div><div class="para">
+ To activate or <span class="quote">“<span class="quote">bring up</span>”</span> an interface to a network team, <span class="interface">team0</span>, using the <span class="application"><strong>ip</strong></span> utility, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ip link set team0 up</code></pre>
+
+ </div></div><div class="section" id="sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.8. Viewing the Active Port Options of a Team Using teamnl</h3></div></div></div><div class="para">
+ To view or list the <code class="option">activeport</code> option in a network team, using the <span class="application"><strong>teamnl</strong></span> utility, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamnl team0 getoption activeport</code>
+0</pre>
+
+ </div></div><div class="section" id="sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.9. Setting the Active Port Options of a Team Using teamnl</h3></div></div></div><div class="para">
+ To set the <code class="option">activeport</code> option in a network team, using the <span class="application"><strong>teamnl</strong></span> utility, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamnl team0 setoption activeport 5</code></pre>
+ To check the change in team port options, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamnl team0 getoption activeport</code>
+5</pre>
+
+ </div></div></div><div class="section" id="sec-Controlling_teamd_with_teamdctl"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.11. Controlling teamd with teamdctl</h2></div></div></div><div class="para">
+ In order to query a running instance of <code class="systemitem">teamd</code> for statistics or configuration information, or to make changes, the control tool <span class="application"><strong>teamdctl</strong></span> is used.
+ </div><div class="para">
+ To view the current team state of a team <span class="interface">team0</span>, enter the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamdctl team0 state view</code></pre>
+ For a more verbose output:
+<pre class="screen">~]# <code class="command">teamdctl team0 state view -v</code></pre>
+ </div><div class="para">
+ For a complete state dump in JSON format (useful for machine processing) of <span class="interface">team0</span>, use the following command:
+<pre class="screen">~]# <code class="command">teamdctl team0 state dump</code></pre>
+ </div><div class="para">
+ For a configuration dump in JSON format of <span class="interface">team0</span>, use the following command:
+<pre class="screen">~]# <code class="command">teamdctl team0 config dump</code></pre>
+ </div><div class="para">
+ To view the configuration of a port <span class="interface">em1</span>, that is part of a team <span class="interface">team0</span>, enter the following command:
+<pre class="screen">~]# <code class="command">teamdctl team0 port config dump em1</code></pre>
+ </div><div class="section" id="sec-Add_a_port_to_a_Network_Team"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.11.1. Add a Port to a Network Team</h3></div></div></div><div class="para">
+ To add a port <span class="interface">em1</span> to a network team <span class="interface">team0</span>, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamdctl team0 port add em1</code></pre>
+
+ </div></div><div class="section" id="sec-Remove_a_Port_From_a_Network_Team"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.11.2. Remove a Port From a Network Team</h3></div></div></div><div class="para">
+ To remove an interface <span class="interface">em1</span> from a network team <span class="interface">team0</span>, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamdctl team0 port remove em1</code></pre>
+
+ </div></div><div class="section" id="sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.11.3. Apply a Configuration to a Port in a Network Team</h3></div></div></div><div class="para">
+ To apply a JSON format configuration to a port <span class="interface">em1</span> in a network team <span class="interface">team0</span>, issue a command as <code class="systemitem">root</code> in the following format:
+<pre class="screen">~]# <code class="command">teamdctl team0 port config update em1 <em class="replaceable"><code>JSON-config-string</code></em></code></pre>
+ Where <em class="replaceable"><code>JSON-config-string</code></em> is the configuration as a string of text in JSON format. This will update the configuration of the port using the JSON format string supplied. An example of a valid JSON string for configuring a port would be the following:
+<pre class="screen">
+{
+ "prio": -10,
+ "sticky": true
+}</pre>
+ Use single quotes around the JSON configuration string and omit the line breaks.
+ </div><div class="para">
+ Note that the old configuration will be overwritten and that any options omitted will be reset to the default values. See the <code class="filename">teamdctl(8)</code> man page for more team daemon control tool command examples.
+ </div></div><div class="section" id="sec-View_the_Configuration_of_a_Port_in_a_Network_Team"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.11.4. View the Configuration of a Port in a Network Team</h3></div></div></div><div class="para">
+ To copy the configuration of a port <span class="interface">em1</span> in a network team <span class="interface">team0</span>, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamdctl team0 port config dump em1</code></pre>
+ This will dump the JSON format configuration of the port to standard output.
+ </div></div></div><div class="section" id="sec-Configure_teamd_Runners"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.12. Configure teamd Runners</h2></div></div></div><div class="para">
+ Runners are units of code which are compiled into the Team daemon when an instance of the daemon is created. For an introduction to the <code class="systemitem">teamd</code> runners, see <a class="xref" href="#sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners">Section 5.4, “Understanding the Network Teaming Daemon and the "Runners"”</a>.
+ </div><div class="section" id="sec-Configure_the_broadcast_Runner"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.1. Configure the broadcast Runner</h3></div></div></div><div class="para">
+ To configure the broadcast runner, using an editor as <code class="systemitem">root</code>, add the following to the team JSON format configuration file:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {"name": "broadcast"},
+ "ports": {"em1": {}, "em2": {}}
+}</pre>
+
+ </div><div class="para">
+ Please see the <code class="filename">teamd.conf(5)</code> man page for more information.
+ </div></div><div class="section" id="sec-Configure_the_random_Runner"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.2. Configure the random Runner</h3></div></div></div><div class="para">
+ The random runner behaves similarly to the roundrobin runner.
+ </div><div class="para">
+ To configure the random runner, using an editor as <code class="systemitem">root</code>, add the following to the team JSON format configuration file:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {"name": "random"},
+ "ports": {"em1": {}, "em2": {}}
+}</pre>
+
+ </div><div class="para">
+ Please see the <code class="filename">teamd.conf(5)</code> man page for more information.
+ </div></div><div class="section" id="sec-Configure_the_roundrobin_Runner"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.3. Configure the roundrobin Runner</h3></div></div></div><div class="para">
+ To configure the roundrobin runner, using an editor as <code class="systemitem">root</code>, add the following to the team JSON format configuration file:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {"name": "roundrobin"},
+ "ports": {"em1": {}, "em2": {}}
+}</pre>
+ A very basic configuration for roundrobin.
+ </div><div class="para">
+ Please see the <code class="filename">teamd.conf(5)</code> man page for more information.
+ </div></div><div class="section" id="sec-Configure_the_activebackup_Runner"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.4. Configure the activebackup Runner</h3></div></div></div><div class="para">
+ The active backup runner can use all of the link-watchers to determine the status of links in a team. Any one of the following examples can be added to the team JSON format configuration file:
+ </div><div class="para">
+
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {
+ "name": "activebackup"
+ },
+ "link_watch": {
+ "name": "ethtool"
+ },
+ "ports": {
+ "em1": {
+ "prio": -10,
+ "sticky": true
+ },
+ "em2": {
+ "prio": 100
+ }
+ }
+}</pre>
+ This example configuration uses the active-backup runner with <span class="application"><strong>ethtool</strong></span> as the link watcher. Port <span class="interface">em2</span> has higher priority. The sticky flag ensures that if <span class="interface">em1</span> becomes active, it stays active as long as the link remains up.
+ </div><div class="para">
+
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {
+ "name": "activebackup"
+ },
+ "link_watch": {
+ "name": "ethtool"
+ },
+ "ports": {
+ "em1": {
+ "prio": -10,
+ "sticky": true,
+ "queue_id": 4
+ },
+ "em2": {
+ "prio": 100
+ }
+ }
+}</pre>
+ This example configuration adds a queue ID of <code class="literal">4</code>. It uses active-backup runner with <span class="application"><strong>ethtool</strong></span> as the link watcher. Port <span class="interface">em2</span> has higher priority. But the sticky flag ensures that if <span class="interface">em1</span> becomes active, it will stay active as long as the link remains up.
+ </div><div class="para">
+ To configure the activebackup runner using <span class="application"><strong>ethtool</strong></span> as the link watcher and applying a delay, using an editor as <code class="systemitem">root</code>, add the following to the team JSON format configuration file:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {
+ "name": "activebackup"
+ },
+ "link_watch": {
+ "name": "ethtool",
+ "delay_up": 2500,
+ "delay_down": 1000
+ },
+ "ports": {
+ "em1": {
+ "prio": -10,
+ "sticky": true
+ },
+ "em2": {
+ "prio": 100
+ }
+ }
+}</pre>
+ This example configuration uses the active-backup runner with <span class="application"><strong>ethtool</strong></span> as the link watcher. Port <span class="interface">em2</span> has higher priority. But the sticky flag ensures that if <span class="interface">em1</span> becomes active, it stays active while the link remains up. Link changes are not propagated to the runner immediately, but delays are applied.
+ </div><div class="para">
+ Please see the <code class="filename">teamd.conf(5)</code> man page for more information.
+ </div></div><div class="section" id="sec-Configure_the_loadbalance_Runner"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.5. Configure the loadbalance Runner</h3></div></div></div><div class="para">
+ This runner can be used for two types of load balancing, active and passive. In active mode, constant re-balancing of traffic is done by using statistics of recent traffic to share out traffic as evenly as possible. In static mode, streams of traffic are distributed randomly across the available links. This has a speed advantage due to lower processing overhead. In high volume traffic applications this is often preferred as traffic usually consists of multiple stream which will be distributed randomly between the available links, in his way load sharing is accomplished without intervention by <code class="systemitem">teamd</code>.
+ </div><div class="para">
+ To configure the loadbalance runner for passive transmit (Tx) load balancing, using an editor as <code class="systemitem">root</code>, add the following to the team JSON format configuration file:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {
+ "name": "loadbalance",
+ "tx_hash": ["eth", "ipv4", "ipv6"]
+ },
+ "ports": {"em1": {}, "em2": {}}
+}</pre>
+ Configuration for hash-based passive transmit (Tx) load balancing.
+ </div><div class="para">
+ To configure the loadbalance runner for active transmit (Tx) load balancing, using an editor as <code class="systemitem">root</code>, add the following to the team JSON format configuration file:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {
+ "name": "loadbalance",
+ "tx_hash": ["eth", "ipv4", "ipv6"],
+ "tx_balancer": {
+ "name": "basic"
+ }
+ },
+ "ports": {"em1": {}, "em2": {}}
+}</pre>
+ Configuration for active transmit (Tx) load balancing using basic load balancer.
+ </div><div class="para">
+ Please see the <code class="filename">teamd.conf(5)</code> man page for more information.
+ </div></div><div class="section" id="sec-Configure_the_LACP_Runner"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.6. Configure the LACP (802.3ad) Runner</h3></div></div></div><div class="para">
+ To configure the LACP runner using <span class="application"><strong>ethtool</strong></span> as a link watcher, using an editor as <code class="systemitem">root</code>, add the following to the team JSON format configuration file:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {
+ "name": "lacp",
+ "active": true,
+ "fast_rate": true,
+ "tx_hash": ["eth", "ipv4", "ipv6"]
+ },
+ "link_watch": {"name": "ethtool"},
+ "ports": {"em1": {}, "em2": {}}
+}</pre>
+ Configuration for connection to a <em class="firstterm">link aggregation control protocol</em> (<acronym class="acronym">LACP</acronym>) capable counterpart. The LACP runner should use <span class="application"><strong>ethtool</strong></span> to monitor the status of a link. It does not make sense to use any other link monitoring method besides the <span class="application"><strong>ethtool</strong></span> because, for example in the case of <span class="application"><strong>arp_ping</strong></span>, the link would never come up. The reason is that the link has to be established first and only after that can packets, ARP included, go through. Using <span class="application"><strong>ethtool</strong></span> prevents this because it monitors each link layer individually.
+ </div><div class="para">
+ Active load balancing is possible with this runner in the same way as it is done for the loadbalance runner. To enable active transmit (Tx) load balancing, add the following section:
+<pre class="screen">"tx_balancer": {
+ "name": "basic"
+}</pre>
+ </div><div class="para">
+ Please see the <code class="filename">teamd.conf(5)</code> man page for more information.
+ </div></div><div class="section" id="sec-Configure_Monitoring_of_the_Link_State"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.7. Configure Monitoring of the Link State</h3></div></div></div><div class="para">
+ The following methods of link state monitoring are available. To implement one of the methods, add the JSON format string to the team JSON format configuration file using an editor running with <code class="systemitem">root</code> privileges.
+ </div><div class="section" id="sec-Configure_Ethtool_for_Link-state_Monitoring"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">5.12.7.1. Configure Ethtool for link-state Monitoring</h4></div></div></div><div class="para">
+ To add or edit an existing delay, in milliseconds, between the link coming up and the runner being notified about it, add or edit a section as follows:
+<pre class="screen">
+"link_watch": {
+ "name": "ethtool",
+ "delay_up": 2500
+}</pre>
+
+ </div><div class="para">
+ To add or edit an existing delay, in milliseconds, between the link going down and the runner being notified about it, add or edit a section as follows:
+<pre class="screen">
+"link_watch": {
+ "name": "ethtool",
+ "delay_down": 1000
+}</pre>
+
+ </div></div><div class="section" id="sec-Configure_ARP_Ping_for_Link-state_Monitoring"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">5.12.7.2. Configure ARP Ping for Link-state Monitoring</h4></div></div></div><div class="para">
+ The team daemon <code class="systemitem">teamd</code> sends an ARP REQUEST to an address at the remote end of the link in order to determine if the link is up. The method used is the same as the <span class="application"><strong>arping</strong></span> utility but it does not use that utility.
+ </div><div class="para">
+ Prepare a file containing the new configuration in JSON format similar to the following example:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {"name": "activebackup"},
+ "link_watch":{
+ "name": "arp_ping",
+ "interval": 100,
+ "missed_max": 30,
+ "source_host": "192.168.23.2",
+ "target_host": "192.168.23.1"
+ },
+ "ports": {
+ "em1": {
+ "prio": -10,
+ "sticky": true
+ },
+ "em2": {
+ "prio": 100
+ }
+ }
+}</pre>
+ This configuration uses <span class="application"><strong>arp_ping</strong></span> as the link watcher. The <code class="option">missed_max</code> option is a limit value of the maximum allowed number of missed replies (ARP replies for example). It should be chosen in conjunction with the <code class="option">interval</code> option in order to determine the total time before a link is reported as down.
+ </div><div class="para">
+ To load a new configuration for a team port <span class="interface">em2</span>, from a file containing a JSON configuration, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# port config update em2 <em class="replaceable"><code>JSON-config-file</code></em></pre>
+ Note that the old configuration will be overwritten and that any options omitted will be reset to the default values. See the <code class="filename">teamdctl(8)</code> man page for more team daemon control tool command examples.
+ </div></div><div class="section" id="sec-Configure_IPv6_NA_NS_for_Link-state_Monitoring"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">5.12.7.3. Configure IPv6 NA/NS for Link-state Monitoring</h4></div></div></div><div class="para">
+
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {"name": "activebackup"},
+ "link_watch": {
+ "name": "nsna_ping",
+ "interval": 200,
+ "missed_max": 15,
+ "target_host": "fe80::210:18ff:feaa:bbcc"
+ },
+ "ports": {
+ "em1": {
+ "prio": -10,
+ "sticky": true
+ },
+ "em2": {
+ "prio": 100
+ }
+ }
+}</pre>
+
+ </div><div class="para">
+ To configure the interval between sending NS/NA packets, add or edit a section as follows:
+<pre class="screen">
+"link_watch": {
+ "name": "nsna_ping",
+ "interval": 200
+}</pre>
+ Value is positive number in milliseconds. It should be chosen in conjunction with the <code class="option">missed_max</code> option in order to determine the total time before a link is reported as down.
+ </div><div class="para">
+ To configure the maximum number of missed NS/NA reply packets to allow before reporting the link as down, add or edit a section as follows:
+<pre class="screen">
+"link_watch": {
+ "name": "nsna_ping",
+ "missed_max": 15
+}</pre>
+ Maximum number of missed NS/NA reply packets. If this number is exceeded, the link is reported as down. The <code class="option">missed_max</code> option is a limit value of the maximum allowed number of missed replies (ARP replies for example). It should be chosen in conjunction with the <code class="option">interval</code> option in order to determine the total time before a link is reported as down.
+ </div><div class="para">
+ To configure the host name that is resolved to the <code class="systemitem">IPv6</code> address target address for the NS/NA packets, add or edit a section as follows:
+<pre class="screen">
+"link_watch": {
+ "name": "nsna_ping",
+ "target_host": "MyStorage"
+}</pre>
+ The <span class="quote">“<span class="quote">target_host</span>”</span> option contains the host name to be converted to an <code class="systemitem">IPv6</code> address which will be used as the target address for the NS/NA packets. An <code class="systemitem">IPv6</code> address can be used in place of a host name.
+ </div><div class="para">
+ Please see the <code class="filename">teamd.conf(5)</code> man page for more information.
+ </div></div></div><div class="section" id="sec-Configure_Port_Selection_Override"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.8. Configure Port Selection Override</h3></div></div></div><div class="para">
+ The physical port which transmits a frame is normally selected by the kernel part of the team driver, and is not relevant to the user or system administrator. The output port is selected using the policies of the selected team mode (<code class="systemitem">teamd</code> runner). On occasion however, it is helpful to direct certain classes of outgoing traffic to certain physical interfaces to implement slightly more complex policies. By default the team driver is multiqueue aware and 16 queues are created when the driver initializes (see <a href="https://www.kernel.org/doc/Documentation/networking/multiqueue.txt">https://www.kernel.org/doc/Documentation/networking/multiqueue.txt</a> for details). If more or less queues are desired, the Netlink attribute <code class="command">tx_queues</code> can be used to change this value during the team driver instance creation.
+ </div><div class="para">
+ The queue ID for a port can be set by the port configuration option <code class="option">queue_id</code> as follows:
+<pre class="screen">
+{
+ "queue_id": 3
+}</pre>
+ These queue ID's can be used in conjunction with the <span class="application"><strong>tc</strong></span> utility to configure a multiqueue queue discipline and filters to bias certain traffic to be transmitted on certain port devices. For example, if using the above configuration and wanting to force all traffic bound to <code class="systemitem">192.168.1.100</code> to use <span class="interface">eth1</span> in the team as its output device, issue commands as <code class="systemitem">root</code> in the following format:
+<pre class="screen">~]# <code class="command">tc qdisc add dev team0 handle 1 root multiq</code>
+~]# <code class="command">tc filter add dev team0 protocol ip parent 1: prio 1 u32 match ip dst \</code>
+<code class="command"> 192.168.1.100 action skbedit queue_mapping 3</code></pre>
+ This mechanism of overriding runner selection logic in order to bind traffic to a specific port can be used with all runners.
+ </div></div><div class="section" id="sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.9. Configure BPF-based Tx Port Selectors</h3></div></div></div><div class="para">
+ The loadbalance and LACP runners uses hashes of packets to sort network traffic flow. The hash computation mechanism is based on the <em class="firstterm">Berkeley Packet Filter</em> (<acronym class="acronym">BPF</acronym>) code. The BPF code is used to generate a hash rather than make a policy decision for outgoing packets. The hash length is 8 bits giving 256 variants. This means many different <em class="firstterm">socket buffers</em> (<acronym class="acronym">SKB</acronym>) can have the same hash and therefore pass traffic over the same link. The use of a short hash is a quick way to sort traffic into different streams for the purposes of load balancing across multiple links. In static mode, the hash is only used to decide out of which port the traffic should be sent. In active mode, the runner will continually reassign hashes to different ports in an attempt to reach a perfect balance.
+ </div><div class="para">
+ The following fragment types or strings can be used for packet Tx hash computation:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">eth</code> — Uses source and destination MAC addresses.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">vlan</code> — Uses VLAN ID.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">ipv4</code> — Uses source and destination <code class="systemitem">IPv4</code> addresses.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">ipv6</code> — Uses source and destination <code class="systemitem">IPv6</code> addresses.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">ip</code> — Uses source and destination <code class="systemitem">IPv4</code> and <code class="systemitem">IPv6</code> addresses.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">l3</code> — Uses source and destination <code class="systemitem">IPv4</code> and <code class="systemitem">IPv6</code> addresses.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">tcp</code> — Uses source and destination <code class="systemitem">TCP</code> ports.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">udp</code> — Uses source and destination <code class="systemitem">UDP</code> ports.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">sctp</code> — Uses source and destination <code class="systemitem">SCTP</code> ports.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">l4</code> — Uses source and destination <code class="systemitem">TCP</code> and <code class="systemitem">UDP</code> and <code class="systemitem">SCTP</code> ports.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ These strings can be used by adding a line in the following format to the load balance runner: <pre class="synopsis">"tx_hash": ["eth", "ipv4", "ipv6"]</pre> See <a class="xref" href="#sec-Configure_the_loadbalance_Runner">Section 5.12.5, “Configure the loadbalance Runner”</a> for an example.
+ </div></div></div><div class="section" id="sec-Configure_Network_Teaming_Using_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.13. Configure Network Teaming Using nmcli</h2></div></div></div><div class="para">
+ To view the devices available on the system, issue the following command:
+<pre class="screen">~]$ <code class="command">nmcli connection show</code>
+NAME UUID TYPE DEVICE
+eth1 0e8185a1-f0fd-4802-99fb-bedbb31c689b 802-3-ethernet --
+eth0 dfe1f57b-419d-4d1c-aaf5-245deab82487 802-3-ethernet --</pre>
+
+ </div><div class="para">
+ To create a new team interface, with name <em class="replaceable"><code>team-ServerA</code></em>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection add type team ifname <em class="replaceable"><code>team-ServerA</code></em></code>
+Connection 'team-ServerA' (b954c62f-5fdd-4339-97b0-40efac734c50) successfully added.</pre>
+ <span class="application"><strong>NetworkManager</strong></span> will set its internal parameter <code class="option">connection.autoconnect</code> to <code class="literal">yes</code> and as no <code class="systemitem">IP</code> address was given <code class="option">ipv4.method</code> will be set to <code class="literal">auto</code>. <span class="application"><strong>NetworkManager</strong></span> will also write a configuration file to <code class="filename">/etc/sysconfig/network-scripts/ifcfg-team-ServerA</code> where the corresponding ONBOOT will be set to <code class="literal">yes</code> and BOOTPROTO will be set to <code class="literal">dhcp</code>.
+ </div><div class="para">
+ Note that manual changes to the ifcfg file will not be noticed by <span class="application"><strong>NetworkManger</strong></span> until the interface is next brought up. See <a class="xref" href="#sec-Network_Configuration_Using_sysconfig_Files">Section 1.7, “Network Configuration Using sysconfig Files”</a> for more information on using configuration files.
+ </div><div class="para">
+ To view the other values assigned, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con show <em class="replaceable"><code>team-ServerA</code></em></code>
+connection.id: team-ServerA
+connection.uuid: b954c62f-5fdd-4339-97b0-40efac734c50
+connection.interface-name: ServerA
+connection.type: team
+connection.autoconnect: yes
+<em class="lineannotation"><span class="lineannotation">…</span></em>
+ipv4.method: auto
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em></pre>
+ As no JSON configuration file was specified the default values apply. See the <code class="filename">teamd.conf(5)</code> man page for more information on the team JSON parameters and their default values. Notice that the name was derived from the interface name by prepending the type. Alternatively, specify a name with the <code class="option">con-name</code> option as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection add type team con-name <em class="replaceable"><code>Team0</code></em> ifname <em class="replaceable"><code>ServerB</code></em></code>
+Connection 'Team0' (5f7160a1-09f6-4204-8ff0-6d96a91218a7) successfully added.</pre>
+ </div><div class="para">
+ To view the team interfaces just configured, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con show</code>
+NAME UUID TYPE DEVICE
+team-ServerA b954c62f-5fdd-4339-97b0-40efac734c50 team ServerA
+eth1 0e8185a1-f0fd-4802-99fb-bedbb31c689b 802-3-ethernet --
+eth0 dfe1f57b-419d-4d1c-aaf5-245deab82487 802-3-ethernet --
+Team0 5f7160a1-09f6-4204-8ff0-6d96a91218a7 team ServerB</pre>
+ </div><div class="para">
+ To change the name assigned to a team, issue a command in the following format: <pre class="synopsis"><code class="command">nmcli con mod <em class="replaceable"><code>old-team-name</code></em> connection.id <em class="replaceable"><code>new-team-name</code></em></code></pre>
+ </div><div class="para">
+ To load a team configuration file for a team that already exists, issue a command in the following format: <pre class="synopsis"><code class="command">nmcli connection modify <em class="replaceable"><code>team-name</code></em> team.config <em class="replaceable"><code>JSON-config</code></em></code></pre> You can specify the team configuration either as a JSON string or provide a file name containing the configuration. The file name can include the path. In both cases, what is stored in the <em class="parameter"><code>team.config</code></em> property is the JSON string. In the case of a JSON string, use single quotes around the string and paste the entire string to the command line.
+ </div><div class="para">
+ To review the <code class="literal">team.config</code> property, enter a command in the following format: <pre class="synopsis"><code class="command">nmcli con show <em class="replaceable"><code>team-name</code></em> | grep team.config</code></pre>
+ </div><div class="para">
+ To add an interface <em class="replaceable"><code>eth0</code></em> to <code class="literal">Team0</code>, with the name <em class="replaceable"><code>Team0-port1</code></em>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type team-slave con-name <em class="replaceable"><code>Team0-port1</code></em> ifname <em class="replaceable"><code>eth0</code></em> master <em class="replaceable"><code>Team0</code></em></code>
+Connection 'Team0-port1' (ccd87704-c866-459e-8fe7-01b06cf1cffc) successfully added.</pre>
+ Similarly, to add another interface, <em class="replaceable"><code>eth1</code></em>, with the name <em class="replaceable"><code>Team0-port2</code></em>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type team-slave con-name <em class="replaceable"><code>Team0-port2</code></em> ifname <em class="replaceable"><code>eth1</code></em> master <em class="replaceable"><code>Team0</code></em></code>
+Connection 'Team0-port2' (a89ccff8-8202-411e-8ca6-2953b7db52dd) successfully added.</pre>
+ At time of writing, <span class="application"><strong>nmcli</strong></span> only supports Ethernet ports.
+ </div><div class="para">
+ In order to bring up a team, the ports must be brought up first as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection up <em class="replaceable"><code>Team0-port1</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/2)</pre>
+
+<pre class="screen">~]$ <code class="command">nmcli connection up <em class="replaceable"><code>Team0-port2</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/3)</pre>
+ </div><div class="para">
+ You can verify that the team interface was brought up by the activation of the ports, as follows:
+<pre class="screen">~]$ <code class="command">ip link</code>
+3: Team0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT
+ link/ether 52:54:00:76:6f:f0 brd ff:ff:ff:ff:ff:f</pre>
+ Alternatively, issue a command to bring up the team as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection up <em class="replaceable"><code>Team0</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/4)</pre>
+
+ </div><div class="para">
+ See <a class="xref" href="#sec-Using_the_NetworkManager_Command_Line_Tool_nmcli">Section 2.4, “Using the NetworkManager Command Line Tool, nmcli”</a> for an introduction to <span class="application"><strong>nmcli</strong></span>
+ </div></div><div class="section" id="sec-Network_Teaming-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.14. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding network teaming.
+ </div><div class="section" id="sec-teamd-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.14.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">teamd(8)</code> man page — Describes the <code class="systemitem">teamd</code> service.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">teamdctl(8)</code> man page — Describes the <code class="systemitem">teamd</code> control tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">teamd.conf(5)</code> man page — Describes the <code class="systemitem">teamd</code> configuration file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">teamnl(8)</code> man page — Describes the <code class="systemitem">teamd</code> Netlink library.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">bond2team(1)</code> man page — Describes a tool to convert bonding options to team.
+ </div></li></ul></div></div><div class="section" id="sec-teamd_docs-online"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.14.2. Online Documentation</h3></div></div></div><div class="para">
+ <div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.libteam.org">http://www.libteam.org</a></span></dt><dd><div class="para">
+ The upstream project.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.w3schools.com/json/json_syntax.asp">http://www.w3schools.com/json/json_syntax.asp</a></span></dt><dd><div class="para">
+ An explanation of JSON syntax.
+ </div></dd></dl></div>
+
+ </div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-Configure_Network_Bridging" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 6. Configure Network Bridging</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sec-Configure_Network_Bridging_Using_a_GUI">6.1. Configure Network Bridging Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_Bridge_Connection">6.1.1. Establishing a Bridge Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Network_Bridging_Using_the_Command_Line_Interface">6.2. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Check_if_Bridging_Kernel_Module_is_Installed">6.2.1. Check if Bridging Kernel Module is Installed</a></span></dt><dt><span class="section"><a href="#sec-Create_a_Network_Bridge">6.2.2. Create a Network Bridge</a></span></dt></dl></dd><dt><span cl
ass="section"><a href="#sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli">6.3. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="#sec-Network_Bridging-additional_resources">6.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Network_Bridging-docs-inst">6.4.1. Installed Documentation</a></span></dt></dl></dd></dl></div><div class="para">
+ A network bridge is a link-layer device which forwards traffic between networks based on MAC addresses. It makes forwarding decisions based on a table of MAC addresses which it builds by listening to network traffic and thereby learning what hosts are connected to each network. A software bridge can be used within a Linux host in order to emulate a hardware bridge, for example in virtualization applications for sharing a NIC with one or more virtual NICs.
+ </div><div class="para">
+ Note that a bridge cannot be established over Wi-Fi networks operating in <em class="firstterm">Ad-Hoc</em> or <em class="firstterm">Infrastructure</em> modes. This is due to the IEEE 802.11 standard that specifies the use of 3-address frames in Wi-Fi for the efficient use of airtime. A system configured to be an <em class="firstterm">access point</em> (<acronym class="acronym">AP</acronym>) running the <code class="systemitem">hostapd</code> can support the necessary 4-address frames.
+ </div><div class="section" id="sec-Configure_Network_Bridging_Using_a_GUI"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. Configure Network Bridging Using a GUI</h2></div></div></div><div class="para">
+ When starting a bridge interface, <span class="application"><strong>NetworkManager</strong></span> waits for at least one port to enter the <span class="quote">“<span class="quote">forwarding</span>”</span> state before beginning any network-dependent <code class="systemitem">IP</code> configuration such as <code class="systemitem">DHCP</code> or <code class="systemitem">IPv6</code> autoconfiguration. Static <code class="systemitem">IP</code> addressing is allowed to proceed before any slaves or ports are connected or begin forwarding packets.
+ </div><div class="section" id="sec-Establishing_a_Bridge_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.1.1. Establishing a Bridge Connection</h3></div></div></div><div class="procedure" id="procedure-Adding_a_New_Bridge_Connection"><h6>Procedure 6.1. Adding a New Bridge Connection</h6><div class="para">
+ You can configure a new Bridge connection by opening the <span class="guilabel"><strong>Network</strong></span> window and selecting the plus symbol below the menu.
+ </div><ol class="1"><li class="step"><div class="para">
+ To use the graphical <span class="application"><strong>Network</strong></span> settings tool, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the plus symbol below the menu. The <span class="guilabel"><strong>Add Network Connection</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Bridge</strong></span> menu entry. The <span class="guilabel"><strong>Editing Bridge connection <em class="replaceable"><code>1</code></em></strong></span> window appears.
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_Bridge_Connection"><h6>Procedure 6.2. Editing an Existing Bridge Connection</h6><div class="para">
+ You can configure an existing bridge connection by opening the <span class="guilabel"><strong>Network</strong></span> window and selecting the name of the connection from the list. Then click the <span class="guibutton"><strong>Edit</strong></span> button.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Bridge</strong></span> connection you want to edit from the left hand menu.
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guilabel"><strong>Options</strong></span> button.
+ </div></li></ol></div><h4 id="bh-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-bridge">Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Five settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types, see the <span class="guilabel"><strong>General</strong></span> tab:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the menu of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to this network when it is available</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="#sec-Connecting_to_a_Network_Automatically">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>All users may connect to this network</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="#sec-System-wide_and_Private_Connection_Profiles">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to VPN when using this connection</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to a VPN connection when it is available. Select the VPN from the dropdown menu.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Firewall Zone</strong></span> — Select the Firewall Zone from the dropdown menu.
+ </div></li></ul></div><div class="section" id="sec-Configuring_the_Bridge_Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">6.1.1.1. Configuring the Bridge Tab</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Interface name</strong></span> </span></dt><dd><div class="para">
+ The name of the interface to the bridge.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Bridged connections</strong></span> </span></dt><dd><div class="para">
+ One or more slave interfaces.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Aging time</strong></span> </span></dt><dd><div class="para">
+ The time, in seconds, a MAC address is kept in the MAC address forwarding database.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Enable STP (Spanning Tree Protocol)</strong></span> </span></dt><dd><div class="para">
+ If required, select the check box to enable <code class="systemitem">STP</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Priority</strong></span> </span></dt><dd><div class="para">
+ The bridge priority; the bridge with the lowest priority will be elected as the root bridge.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Forward delay</strong></span> </span></dt><dd><div class="para">
+ The time, in seconds, spent in both the Listening and Learning states before entering the Forwarding state. The default is 15 seconds.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Hello time</strong></span> </span></dt><dd><div class="para">
+ The time interval, in seconds, between sending configuration information in bridge protocol data units (BPDU).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Max age</strong></span> </span></dt><dd><div class="para">
+ The maximum time, in seconds, to store the configuration information from BPDUs. This value should be twice the Hello Time plus 1 but less than twice the Forwarding delay minus 1.
+ </div></dd></dl></div><div class="figure" id="exam--Establishing_a_Bridge_Connection"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Editing-Bridge-Connection-1_Gnome3.png"><img src="images/Editing-Bridge-Connection-1_Gnome3.png" alt="Editing Bridge Connection 1" /><div class="longdesc"><div class="para">
+ A screen shot of the Editing Bridge Connection 1
+ </div></div></div></div><h6>Figure 6.1. Editing Bridge Connection 1</h6></div><br class="figure-break" /><div class="procedure" id="procedure-Adding_a_Slave_Interface_to_a_Bridge"><h6>Procedure 6.3. Adding a Slave Interface to a Bridge</h6><ol class="1"><li class="step"><div class="para">
+ To add a port to a bridge, select the <span class="guilabel"><strong>Bridge</strong></span> tab in the <span class="guilabel"><strong>Editing Bridge connection <em class="replaceable"><code>1</code></em></strong></span> window. If necessary, open this window by following the procedure in <a class="xref" href="#procedure-Editing_an_Existing_Bridge_Connection">Procedure 6.2, “Editing an Existing Bridge Connection”</a>.
+ </div></li><li class="step"><div class="para">
+ Click <span class="guibutton"><strong>Add</strong></span>. The <span class="guilabel"><strong>Choose a Connection Type</strong></span> menu appears.
+ </div></li><li class="step"><div class="para">
+ Select the type of connection to be created from the list. Click <span class="guilabel"><strong>Create</strong></span>. A window appropriate to the connection type selected appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Bridge Port</strong></span> tab. Configure <span class="guilabel"><strong>Priority</strong></span> and <span class="guilabel"><strong>Path cost</strong></span> as required. Note the STP priority for a bridge port is limited by the Linux kernel. Although the standard allows a range of <code class="literal">0</code> to <code class="literal">255</code>, Linux only allows <code class="literal">0</code> to <code class="literal">63</code>. The default is <code class="literal">32</code> in this case.
+ </div></li><li class="step"><div class="para">
+ If required, select the <span class="guilabel"><strong>Hairpin mode</strong></span> check box to enable forwarding of frames for external processing. Also known as <em class="firstterm">virtual Ethernet port aggregator</em> (<acronym class="acronym">VEPA</acronym>) mode.
+ </div></li></ol></div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ An Ethernet slave, click the <span class="guilabel"><strong>Ethernet</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-wired">Section 2.2.5.1, “Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings”</a>, or;
+ </div></li><li class="listitem"><div class="para">
+ A Bond slave, click the <span class="guilabel"><strong>Bond</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_the_Bond_Tab">Section 4.2.1.1, “Configuring the Bond Tab”</a>, or;
+ </div></li><li class="listitem"><div class="para">
+ A Team slave, click the <span class="guilabel"><strong>Team</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_the_Team_Tab">Section 5.9.1.1, “Configuring the Team Tab”</a>, or;
+ </div></li><li class="listitem"><div class="para">
+ An VLAN slave, click the <span class="guilabel"><strong>VLAN</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_the_VLAN_Tab">Section 7.2.1.1, “Configuring the VLAN Tab”</a>, or;
+ </div></li></ul></div><h5 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-bridge">Saving Your New (or Modified) Connection and Making Further Configurations</h5><div class="para">
+ Once you have finished editing your new bridge connection, click the <span class="guibutton"><strong>Save</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network</strong></span> window and clicking <span class="guilabel"><strong>Options</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>, or;
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv6</code> settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv6_Settings">Section 2.2.10.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div></div></div></div><div class="section" id="sec-Network_Bridging_Using_the_Command_Line_Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.2. Using the Command Line Interface (CLI)</h2></div></div></div><div class="section" id="sec-Check_if_Bridging_Kernel_Module_is_Installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.2.1. Check if Bridging Kernel Module is Installed</h3></div></div></div><div class="para">
+ In Fedora, the bridging module is loaded by default. If necessary, you can make sure that the module is loaded by issuing the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">modprobe --first-time bridge</code>
+modprobe: ERROR: could not insert 'bridge': Module already in kernel</pre>
+ To display information about the module, issue the following command:
+<pre class="screen">~]$ <code class="command">modinfo bridge</code></pre>
+ See the <code class="filename">modprobe(8)</code> man page for more command options.
+ </div></div><div class="section" id="sec-Create_a_Network_Bridge"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.2.2. Create a Network Bridge</h3></div></div></div><div class="para">
+ To create a network bridge, create a file in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory called <code class="filename">ifcfg-br<em class="replaceable"><code>N</code></em></code>, replacing <em class="replaceable"><code>N</code></em> with the number for the interface, such as <code class="filename">0</code>.
+ </div><div class="para">
+ The contents of the file is similar to whatever type of interface is getting bridged to, such as an Ethernet interface. The differences in this example are as follows:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="option">DEVICE</code> directive is given an interface name as its argument in the format <code class="option">br<em class="replaceable"><code>N</code></em></code>, where <em class="replaceable"><code>N</code></em> is replaced with the number of the interface.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">TYPE</code> directive is given an argument <code class="option">Bridge</code> or <code class="option">Ethernet</code>. This directive determines the device type and the argument is case sensitive.
+ </div></li><li class="listitem"><div class="para">
+ The bridge interface configuration file is given an <code class="systemitem">IP</code> address whereas the physical interface configuration file must only have a MAC address (see below).
+ </div></li><li class="listitem"><div class="para">
+ An extra directive, <code class="option">DELAY=0</code>, is added to prevent the bridge from waiting while it monitors traffic, learns where hosts are located, and builds a table of MAC addresses on which to base its filtering decisions. The default delay of 30 seconds is not needed if no routing loops are possible.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">NM_CONTROLLED=no</code> should be added to the Ethernet interface to prevent <span class="application"><strong>NetworkManager</strong></span> from altering the file. It can also be added to the bridge configuration file.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The following is a sample bridge interface configuration file using a static <code class="systemitem">IP</code> address:
+ </div><div class="example" id="ex-Sample_ifcfg-br0_Interface_Configuration_File"><h6>Example 6.1. Sample ifcfg-br0 Interface Configuration File</h6><div class="example-contents"><pre class="programlisting">DEVICE=br0
+TYPE=Bridge
+IPADDR=192.168.1.1
+PREFIX=24
+ONBOOT=yes
+BOOTPROTO=none
+NM_CONTROLLED=no
+DELAY=0</pre></div></div><br class="example-break" /><div class="para">
+ To complete the bridge another interface is created, or an existing interface is modified, and pointed to the bridge interface. The following is a sample Ethernet interface configuration file pointing to a bridge interface. Configure your physical interface in <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth<em class="replaceable"><code>X</code></em></code>, where <em class="replaceable"><code>X</code></em> is a unique number corresponding to a specific interface, as follows:
+ </div><div class="example" id="ex-Sample_ifcfg-eth0_Interface_Configuration_File"><h6>Example 6.2. Sample ifcfg-ethX Interface Configuration File</h6><div class="example-contents"><pre class="programlisting">DEVICE=ethX
+TYPE=Ethernet
+HWADDR=AA:BB:CC:DD:EE:FF
+BOOTPROTO=none
+ONBOOT=yes
+NM_CONTROLLED=no
+BRIDGE=br0</pre></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ For the <code class="option">DEVICE</code> directive, almost any interface name could be used as it does not determine the device type. <code class="option">TYPE=Ethernet</code> is not strictly required. If the <code class="option">TYPE</code> directive is not set, the device is treated as an Ethernet device (unless it's name explicitly matches a different interface configuration file.)
+ </div></div></div><div class="para">
+ Specifying the hardware or MAC address using the <code class="command">HWADDR</code> directive will influence the device naming procedure as explained in <a class="xref" href="#ch-Consistent_Network_Device_Naming">Chapter 8, <em>Consistent Network Device Naming</em></a>.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ If you are configuring bridging on a remote host, and you are connected to that host over the physical NIC you are configuring, please consider the implications of losing connectivity before proceeding. You will lose connectivity when restarting the service and may not be able to regain connectivity if any errors have been made. Console, or out-of-band access is advised.
+ </div></div></div><div class="para">
+ Restart the networking service in order for the changes to take effect. As <code class="systemitem">root</code> issue the following command:
+ </div><pre class="screen">~]# <code class="command">systemctl network restart</code></pre><div class="para">
+ An example of a network bridge formed from two or more bonded Ethernet interfaces will now be given as this is another common application in a virtualization environment. If you are not very familiar with the configuration files for bonded interfaces then please refer to <a class="xref" href="#sec-Create_a_Channel_Bonding_Interface">Section 4.3.2, “Create a Channel Bonding Interface”</a>
+ </div><div class="para">
+ Create or edit two or more Ethernet interface configuration files, which are to be bonded, as follows:
+<pre class="programlisting">DEVICE=ethX
+TYPE=Ethernet
+SLAVE=yes
+MASTER=bond0
+BOOTPROTO=none
+HWADDR=AA:BB:CC:DD:EE:FF
+NM_CONTROLLED=no</pre>
+
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Using <code class="systemitem">eth<em class="replaceable"><code>X</code></em></code> as the interface name is common practice but almost any name could be used.
+ </div></div></div><div class="para">
+ Create or edit one interface configuration file, <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond0</code>, as follows:
+<pre class="programlisting">DEVICE=bond0
+ONBOOT=yes
+BONDING_OPTS='mode=1 miimon=100'
+BRIDGE=brbond0
+NM_CONTROLLED=no</pre>
+
+ </div><div class="para">
+ Create or edit one interface configuration file, <code class="filename">/etc/sysconfig/network-scripts/ifcfg-brbond0</code>, as follows:
+<pre class="programlisting">DEVICE=brbond0
+ONBOOT=yes
+TYPE=Bridge
+IPADDR=192.168.1.1
+PREFIX=24
+NM_CONTROLLED=no</pre>
+
+ </div><div class="para">
+ We now have two or more interface configuration files with the <code class="option">MASTER=bond0</code> directive. These point to the configuration file named <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond0</code>, which contains the <code class="option">DEVICE=bond0</code> directive. This <code class="filename">ifcfg-bond0</code> in turn points to the <code class="filename">/etc/sysconfig/network-scripts/ifcfg-brbond0</code> configuration file, which contains the <code class="systemitem">IP</code> address, and acts as an interface to the virtual networks inside the host.
+ </div><div class="para">
+ Restart the networking service, in order for the changes to take effect. As <code class="systemitem">root</code> issue the following command:
+ </div><pre class="screen">~]# <code class="command">systemctl network restart</code></pre></div></div><div class="section" id="sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.3. Using the NetworkManager Command Line Tool, nmcli</h2></div></div></div><div class="para">
+ To create a bridge, with name <span class="interface">bridge-br0</span>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type bridge ifname br0</code>
+Connection 'bridge-br0' (79cf6a3e-0310-4a78-b759-bda1cc3eef8d) successfully added.</pre>
+ If no interface name is specified, the name will default to <span class="interface">bridge</span>, <span class="interface">bridge-1</span>, <span class="interface">bridge-2</span>, and so on.
+ </div><div class="para">
+ To view the connections, issue the following command:
+<pre class="screen">~]$ <code class="command">nmcli con show conf</code>
+NAME UUID TYPE TIMESTAMP-REAL
+eth0 4d5c449a-a6c5-451c-8206-3c9a4ec88bca 802-3-ethernet Mon 21 Oct 2013 16:01:53 BST
+bridge-br0 79cf6a3e-0310-4a78-b759-bda1cc3eef8d bridge never</pre>
+
+ </div><div class="para">
+ <em class="firstterm">Spanning tree protocol</em> (<acronym class="acronym">STP</acronym>) according to the IEEE 802.1D standard is enabled by default. To disable <code class="systemitem">STP</code> for this bridge, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con bridge-br0 stp no</code></pre>
+ To re-enable <code class="systemitem">802.1D STP</code> for this bridge, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con bridge-br0 stp yes</code></pre>
+
+ </div><div class="para">
+ The default bridge priority for <code class="systemitem">802.1D STP</code> is <code class="literal">32768</code>. The lower number is preferred in root bridge selection. For example, a bridge with priority of <code class="literal">28672</code> would be selected as the root bridge in preference to a bridge with priority value of <code class="literal">32768</code> (the default). To create a bridge with a non-default value, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type bridge ifname br5 stp yes priority 28672</code>
+Connection 'bridge-br5' (86b83ad3-b466-4795-aeb6-4a66eb1856c7) successfully added.</pre>
+ The allowed values are in the range <code class="literal">0</code> to <code class="literal">65535</code>, but can only be set in multiples of <code class="literal">4096</code>.
+ </div><div class="para">
+ To change the bridge priority of an existing bridge to a non-default value, issue a command in the following format:
+<pre class="screen">~]$ <code class="command">nmcli connection modify bridge-br5 bridge.priority 36864</code></pre>
+ The allowed values are in the range <code class="literal">0</code> to <code class="literal">65535</code>, but can only be set in multiples of <code class="literal">4096</code>.
+ </div><div class="para">
+ Further options for <code class="systemitem">802.1D STP</code> are listed in the bridge section of the <code class="filename">nmcli(1)</code> man page.
+ </div><div class="para">
+ To add, or enslave an interface, for example <span class="interface">eth1</span>, to the bridge <span class="interface">bridge-br0</span>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type bridge-slave ifname eth1 master bridge-br0</code>
+Connection 'bridge-slave-eth1' (70ffae80-7428-4d9c-8cbd-2e35de72476e) successfully added.</pre>
+ At time of writing, <span class="application"><strong>nmcli</strong></span> only supports Ethernet slaves.
+ </div><div class="para">
+ To change a value using interactive mode, issue the following command:
+<pre class="screen">~]$ <code class="command">nmcli connection edit bridge-br0</code></pre>
+ You will be placed at the <span class="application"><strong>nmcli</strong></span> prompt.
+<pre class="screen">nmcli> <code class="command">set bridge.priority 4096</code>
+nmcli> <code class="command">save</code>
+Connection 'bridge-br0' (79cf6a3e-0310-4a78-b759-bda1cc3eef8d) successfully saved.
+nmcli> <code class="command">quit</code></pre>
+
+ </div><div class="para">
+ See <a class="xref" href="#sec-Using_the_NetworkManager_Command_Line_Tool_nmcli">Section 2.4, “Using the NetworkManager Command Line Tool, nmcli”</a> for an introduction to <span class="application"><strong>nmcli</strong></span>
+ </div></div><div class="section" id="sec-Network_Bridging-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.4. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding network bridging.
+ </div><div class="section" id="sec-Network_Bridging-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.4.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">nmcli(1)</code> man page — Describes <span class="application"><strong>NetworkManager</strong></span>'s command‐line tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nmcli-examples(5)</code> man page — Gives examples of <span class="application"><strong>nmcli</strong></span> commands.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nm-settings(5)</code> man page — Description of settings and parameters of <span class="application"><strong>NetworkManager</strong></span> connections.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-Configure_802_1Q_VLAN_Tagging" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 7. Configure 802.1Q VLAN tagging</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sec-Selecting_VLAN_Interface_Configuration_Methods">7.1. Selecting VLAN Interface Configuration Methods</a></span></dt><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI">7.2. Configure 802.1Q VLAN Tagging Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_VLAN_Connection">7.2.1. Establishing a VLAN Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line">7.3. Configure 802.1Q VLAN Tagging Using the Command Line</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_Up_802.1Q_VLAN_Tagging_Using_ifcfg_Files
">7.3.1. Setting Up 802.1Q VLAN Tagging Using ifcfg Files</a></span></dt><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging_ip_Commands">7.3.2. Configure 802.1Q VLAN Tagging Using ip Commands</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli">7.4. Configure 802.1Q VLAN Tagging Using the Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging-additional_resources">7.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configure_802_1Q_VLAN_Tagging-docs-inst">7.5.1. Installed Documentation</a></span></dt></dl></dd></dl></div><div class="para">
+ To create a VLAN, an interface is created on another interface referred to as the <em class="firstterm">parent interface</em>. The VLAN interface will tag packets with the VLAN ID as they pass through the interface, and returning packets will be untagged. VLAN interface can be configured similarly to any other interface. The parent interface need not be an Ethernet interface. An 802.1Q VLAN tagging interface can be created on bridge, bond, and team interfaces, however there are some things to note:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ In the case of VLANs over bonds, it is important that the bond has slaves and that they are <span class="quote">“<span class="quote">up</span>”</span> before bringing up the VLAN interface. At the time of writing, adding a VLAN interface to a bond without slaves does not work.
+ </div></li><li class="listitem"><div class="para">
+ A VLAN slave cannot be configured on a bond with the <code class="option">fail_over_mac=follow</code> option, because the VLAN virtual device cannot change its MAC address to match the parent's new MAC address. In such a case, traffic would still be sent with the now incorrect source MAC address.
+ </div></li><li class="listitem"><div class="para">
+ Sending VLAN tagged packets through a network switch requires configuration of the switch. Refer to the documentation for the switch. For example, for Cisco switches the port must be assigned to one VLAN or configured to be a trunk port to accept tagged packets for multiple VLANs. Untagged packets can also be processed by a trunk port and processed as belonging to the <em class="firstterm">native VLAN</em>, however this is a security risk and may have been disabled, or by default not enabled, depending on the make of the switch.
+ </div></li><li class="listitem"><div class="para">
+ Some older network interface cards, loopback interfaces, Wimax cards, and some InfiniBand devices, are said to be <em class="firstterm">VLAN challenged</em>, meaning they cannot support VLANs. This is usually because the devices cannot cope with VLAN headers and the larger MTU size associated with tagged packets.
+ </div></li></ul></div><div class="section" id="sec-Selecting_VLAN_Interface_Configuration_Methods"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.1. Selecting VLAN Interface Configuration Methods</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>To configure a network using graphical user interface tools</strong></span>, proceed to <a class="xref" href="#sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI">Section 7.2, “Configure 802.1Q VLAN Tagging Using a GUI”</a>
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>To configure a VLAN interface using</strong></span> <span class="application"><strong>NetworkManager</strong></span>'s command-line tool, <span class="application"><strong>nmcli</strong></span>, proceed to <a class="xref" href="#sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli">Section 7.4, “Configure 802.1Q VLAN Tagging Using the Command Line Tool, nmcli”</a>
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>To configure a network interface manually</strong></span>, see <a class="xref" href="#sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line">Section 7.3, “Configure 802.1Q VLAN Tagging Using the Command Line”</a>.
+ </div></li></ul></div></div><div class="section" id="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.2. Configure 802.1Q VLAN Tagging Using a GUI</h2></div></div></div><div class="section" id="sec-Establishing_a_VLAN_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.1. Establishing a VLAN Connection</h3></div></div></div><div class="para">
+ You can use the GNOME <span class="application"><strong>control-center</strong></span> utility to direct <span class="application"><strong>NetworkManager</strong></span> to create a VLAN using an existing interface as the parent interface. At time of writing, you can only make VLANs on Ethernet devices. Note that VLAN devices are only created automatically if the parent interface is set to connect automatically.
+ </div><div class="procedure" id="procedure-Adding_a_New_VLAN_Connection"><h6>Procedure 7.1. Adding a New VLAN Connection</h6><div class="para">
+ You can configure a VLAN connection by opening the <span class="guilabel"><strong>Network</strong></span> window, clicking the plus symbol, and selecting <span class="guilabel"><strong>VLAN</strong></span> from the list.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Click the plus symbol to open the selection list. Select <span class="guilabel"><strong>VLAN</strong></span>. The <span class="guilabel"><strong>Editing VLAN Connection <em class="replaceable"><code>1</code></em></strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ On the <span class="guilabel"><strong>VLAN</strong></span> tab, select the parent interface from the drop-down list you want to use for the VLAN connection.
+ </div></li><li class="step"><div class="para">
+ Enter the VLAN ID
+ </div></li><li class="step"><div class="para">
+ Enter a VLAN interface name. This is the name of the VLAN interface that will be created. For example, <code class="literal">eth0.1</code> or <code class="literal">vlan2</code>. (Normally this is either the parent interface name plus <span class="quote">“<span class="quote"><code class="literal">.</code></span>”</span> and the VLAN ID, or <span class="quote">“<span class="quote"><code class="literal">vlan</code></span>”</span> plus the VLAN ID.)
+ </div></li><li class="step"><div class="para">
+ Review and confirm the settings and then click the <span class="guilabel"><strong>Save</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ To edit the VLAN-specific settings see <a class="xref" href="#sec-Configuring_the_VLAN_Tab">Section 7.2.1.1, “Configuring the VLAN Tab”</a>.
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_VLAN_Connection"><h6>Procedure 7.2. Editing an Existing VLAN Connection</h6><div class="para">
+ Follow these steps to edit an existing VLAN connection.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the connection you want to edit and click the <span class="guilabel"><strong>Options</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>General</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Configure the connection name, auto-connect behavior, and availability settings.
+ </div><div class="para">
+ These settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the <span class="guilabel"><strong>VLAN</strong></span> section of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to this network when it is available</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. Refer to <a class="xref" href="#sec-Connecting_to_a_Network_Automatically">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="#sec-System-wide_and_Private_Connection_Profiles">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li></ul></div></li><li class="step"><div class="para">
+ To edit the VLAN-specific settings see <a class="xref" href="#sec-Configuring_the_VLAN_Tab">Section 7.2.1.1, “Configuring the VLAN Tab”</a>.
+ </div></li></ol></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-VLAN">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your VLAN connection, click the <span class="guibutton"><strong>Save</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network</strong></span> window and clicking <span class="guilabel"><strong>Options</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>.
+ </div></li></ul></div><div class="section" id="sec-Configuring_the_VLAN_Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.2.1.1. Configuring the VLAN Tab</h4></div></div></div><div class="para">
+ If you have already added a new VLAN connection (refer to <a class="xref" href="#procedure-Adding_a_New_VLAN_Connection">Procedure 7.1, “Adding a New VLAN Connection”</a> for instructions), you can edit the <span class="guilabel"><strong>VLAN</strong></span> tab to set the parent interface and the VLAN ID.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Parent Interface</strong></span> </span></dt><dd><div class="para">
+ A previously configured interface can be selected in the drop-down list.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>VLAN ID</strong></span> </span></dt><dd><div class="para">
+ The identification number to be used to tag the VLAN network traffic.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>VLAN interface name</strong></span> </span></dt><dd><div class="para">
+ The name of the VLAN interface that will be created. For example, <code class="literal">eth0.1</code> or <code class="literal">vlan2</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Cloned MAC address</strong></span> </span></dt><dd><div class="para">
+ Optionally sets an alternate MAC address to use for identifying the VLAN interface. This can be used to change the source MAC address for packets sent on this VLAN.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>MTU</strong></span> </span></dt><dd><div class="para">
+ Optionally sets a Maximum Transmission Unit (MTU) size to be used for packets to be sent over the VLAN connection.
+ </div></dd></dl></div></div></div></div><div class="section" id="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.3. Configure 802.1Q VLAN Tagging Using the Command Line</h2></div></div></div><div class="para">
+ In Fedora, the <code class="systemitem">8021q</code> module is loaded by default. If necessary, you can make sure that the module is loaded by issuing the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">modprobe --first-time 8021q</code>
+modprobe: ERROR: could not insert '8021q': Module already in kernel</pre>
+ To display information about the module, issue the following command:
+<pre class="screen">~]$ <code class="command">modinfo 8021q</code></pre>
+ See the <code class="filename">modprobe(8)</code> man page for more command options.
+ </div><div class="section" id="sec-Setting_Up_802.1Q_VLAN_Tagging_Using_ifcfg_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.1. Setting Up 802.1Q VLAN Tagging Using ifcfg Files</h3></div></div></div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Configure the parent interface in <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth<em class="replaceable"><code>X</code></em></code>, where <em class="replaceable"><code>X</code></em> is a unique number corresponding to a specific interface, as follows:
+ </div><pre class="screen">DEVICE=ethX
+TYPE=Ethernet
+BOOTPROTO=none
+ONBOOT=yes</pre></li><li class="step"><div class="para">
+ Configure the VLAN interface configuration in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory. The configuration file name should be the parent interface plus a <code class="literal">.</code> character plus the VLAN ID number. For example, if the VLAN ID is 192, and the parent interface is <em class="replaceable"><code>eth0</code></em>, then the configuration file name should be <code class="filename">ifcfg-eth0.192</code>:
+ </div><pre class="screen">DEVICE=ethX.192
+BOOTPROTO=none
+ONBOOT=yes
+IPADDR=192.168.1.1
+PREFIX=24
+NETWORK=192.168.1.0
+VLAN=yes</pre><div class="para">
+ If there is a need to configure a second VLAN, with for example, VLAN ID 193, on the same interface, <em class="replaceable"><code>eth0</code></em>, add a new file with the name <code class="filename">eth0.193</code> with the VLAN configuration details.
+ </div></li><li class="step"><div class="para">
+ Restart the networking service in order for the changes to take effect. As <code class="systemitem">root</code> issue the following command:
+ </div><pre class="screen">~]# <code class="command">systemctl restart network</code></pre></li></ol></div></div><div class="section" id="sec-Configure_802_1Q_VLAN_Tagging_ip_Commands"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.2. Configure 802.1Q VLAN Tagging Using ip Commands</h3></div></div></div><div class="para">
+ To create an 802.1Q VLAN interface on Ethernet interface <em class="replaceable"><code>eth0</code></em>, with name <em class="replaceable"><code>VLAN8</code></em> and ID <code class="literal">8</code>, issue a command as <code class="systemitem">root</code> as follows:
+<pre class="screen">~]# <code class="command">ip link add link <em class="replaceable"><code>eth0</code></em> name <em class="replaceable"><code>eth0.8</code></em> type vlan id 8</code></pre>
+ To view the VLAN, issue the following command:
+<pre class="screen">~]$ <code class="command">ip -d link show <em class="replaceable"><code>eth0.8</code></em></code>
+4: eth0.8 at eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT
+ link/ether 52:54:00:ce:5f:6c brd ff:ff:ff:ff:ff:ff promiscuity 0
+ vlan protocol 802.1Q id 8 <REORDER_HDR></pre>
+ </div><div class="para">
+ Note that the <span class="application"><strong>ip</strong></span> utility interprets the VLAN ID as a hexadecimal value if it is preceded by <code class="literal">0x</code> and as an octal value if it has a leading <code class="literal">0</code>. This means that in order to assign a VLAN ID with a decimal value of <code class="literal">22</code>, you must not add any leading zeros.
+ </div><div class="para">
+ To remove the VLAN, issue a command as <code class="systemitem">root</code> as follows:
+<pre class="screen">~]# <code class="command">ip link delete <em class="replaceable"><code>eth0.8</code></em></code></pre>
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ VLAN interfaces created using <span class="application"><strong>ip</strong></span> commands at the command prompt will be lost if the system is shutdown or restarted. To configure VLAN interfaces to be persistent after a system restart, use <code class="filename">ifcfg</code> files. See <a class="xref" href="#sec-Setting_Up_802.1Q_VLAN_Tagging_Using_ifcfg_Files">Section 7.3.1, “Setting Up 802.1Q VLAN Tagging Using ifcfg Files”</a>
+ </div></div></div></div></div><div class="section" id="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.4. Configure 802.1Q VLAN Tagging Using the Command Line Tool, nmcli</h2></div></div></div><div class="para">
+ To view the available interfaces on the system, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con show</code>
+NAME UUID TYPE DEVICE
+System eth1 9c92fad9-6ecb-3e6c-eb4d-8a47c6f50c04 802-3-ethernet eth1
+System eth0 5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 802-3-ethernet eth0</pre>
+ Note that the NAME field in the output always denotes the connection ID. It is not the interface name even though it might look the same. The ID can be used in <code class="command">nmcli connection</code> commands to identify a connection. Use the DEVICE name with other applications such as <code class="systemitem">firewalld</code>.
+ </div><div class="para">
+ To create an 802.1Q VLAN interface on Ethernet interface <em class="replaceable"><code>eth0</code></em>, with VLAN interface <em class="replaceable"><code>VLAN10</code></em> and ID <code class="literal">10</code>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type vlan ifname <em class="replaceable"><code>VLAN10</code></em> dev <em class="replaceable"><code>eth0</code></em> id 10</code>
+Connection 'vlan-VLAN10' (37750b4a-8ef5-40e6-be9b-4fb21a4b6d17) successfully added.</pre>
+ Note that as no <code class="option">con-name</code> was given for the VLAN interface, the name was derived from the interface name by prepending the type. Alternatively, specify a name with the <code class="option">con-name</code> option as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type vlan con-name <em class="replaceable"><code>VLAN12</code></em> dev <em class="replaceable"><code>eth0</code></em> id 12</code>
+Connection 'VLAN12' (b796c16a-9f5f-441c-835c-f594d40e6533) successfully added.</pre>
+ </div><h3 id="bh-Assigning_Addresses_to_VLAN_Interfaces">Assigning Addresses to VLAN Interfaces</h3><div class="para">
+ You can use the same <span class="application"><strong>nmcli</strong></span> commands to assign static and dynamic interface addresses as with any other interface.
+ </div><div class="para">
+ For example, a command to create a VLAN interface with a static <code class="systemitem">IPv4</code> address and gateway is as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type vlan con-name <em class="replaceable"><code>VLAN20</code></em> ifname <em class="replaceable"><code>eth0</code></em> ip4 10.10.10.10/24 \</code>
+<code class="command">gw4 10.10.10.254</code></pre>
+ </div><div class="para">
+ To create a VLAN interface with dynamically assigned addressing, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type vlan con-name <em class="replaceable"><code>VLAN30</code></em> ifname <em class="replaceable"><code>eth0</code></em></code></pre>
+
+ </div><div class="para">
+ See <a class="xref" href="#sec-Connecting_to_a_Network_Using_nmcli">Section 2.4.2, “Connecting to a Network Using nmcli”</a> for examples of using <span class="application"><strong>nmcli</strong></span> commands to configure interfaces.
+ </div><div class="para">
+ To review the VLAN interfaces created, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con show</code>
+NAME UUID TYPE DEVICE
+VLAN12 4129a37d-4feb-4be5-ac17-14a193821755 vlan eth0.12
+System eth1 9c92fad9-6ecb-3e6c-eb4d-8a47c6f50c04 802-3-ethernet eth1
+System eth0 5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 802-3-ethernet eth0
+vlan-VLAN10 1be91581-11c2-461a-b40d-893d42fed4f4 vlan VLAN10</pre>
+
+ </div><div class="para">
+ To view detailed information about the newly configured connection, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli -p con show <em class="replaceable"><code>VLAN12</code></em></code>
+===============================================================================
+ Connection profile details (VLAN12)
+===============================================================================
+connection.id: VLAN12
+connection.uuid: 4129a37d-4feb-4be5-ac17-14a193821755
+connection.interface-name: --
+connection.type: vlan
+connection.autoconnect: yes
+<em class="lineannotation"><span class="lineannotation">…</span></em>
+-------------------------------------------------------------------------------
+802-3-ethernet.port: --
+802-3-ethernet.speed: 0
+802-3-ethernet.duplex: --
+802-3-ethernet.auto-negotiate: yes
+802-3-ethernet.mac-address: --
+802-3-ethernet.cloned-mac-address: --
+802-3-ethernet.mac-address-blacklist:
+802-3-ethernet.mtu: auto
+<em class="lineannotation"><span class="lineannotation">…</span></em>
+vlan.interface-name: --
+vlan.parent: eth0
+vlan.id: 12
+vlan.flags: 0 (NONE)
+vlan.ingress-priority-map:
+vlan.egress-priority-map:
+-------------------------------------------------------------------------------
+===============================================================================
+ Activate connection details (4129a37d-4feb-4be5-ac17-14a193821755)
+===============================================================================
+GENERAL.NAME: VLAN12
+GENERAL.UUID: 4129a37d-4feb-4be5-ac17-14a193821755
+GENERAL.DEVICES: eth0.12
+GENERAL.STATE: activating
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em></pre>
+ </div><div class="para">
+ Further options for the VLAN command are listed in the VLAN section of the <code class="filename">nmcli(1)</code> man page. In the man pages the device on which the VLAN is created is referred to as the parent device. In the example above the device was specified by its interface name, <code class="literal">eth0</code>, it can also be specified by the connection UUID or MAC address.
+ </div><div class="para">
+ To create an 802.1Q VLAN connection profile with ingress priority mapping on Ethernet interface <em class="replaceable"><code>eth1</code></em>, with name <span class="interface">VLAN1</span> and ID <code class="literal">13</code>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type vlan con-name <em class="replaceable"><code>VLAN1</code></em> dev <em class="replaceable"><code>eth2</code></em> id 13 ingress "2:3,3:5"</code></pre>
+
+ </div><div class="para">
+ To view all the parameters associated with the VLAN created above, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection show <em class="replaceable"><code>vlan-VLAN10</code></em></code></pre>
+
+ </div><div class="para">
+ To change the MTU, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection modify <em class="replaceable"><code>vlan-VLAN10</code></em> 802.mtu 1496</code></pre>
+ The MTU setting determines the maximum size of the network layer packet. The maximum size of the payload the link-layer frame can carry in turn limits the network layer MTU. For standard Ethernet frames this means an MTU of 1500 bytes. It should not be necessary to change the MTU when setting up a VLAN as the link-layer header is increased in size by 4 bytes to accommodate the 802.1Q tag.
+ </div><div class="para">
+ At time of writing, <code class="literal">connection.interface-name</code> and <code class="literal">vlan.interface-name</code> have to be the same (if they are set). They must therefore be changed simultaneously using <span class="application"><strong>nmcli</strong></span>'s interactive mode. To change a VLAN connections name, issue commands as follows:
+<pre class="screen">~]$ <code class="command">nmcli con edit <em class="replaceable"><code>vlan-VLAN10</code></em></code>
+nmcli> <code class="command">set vlan.interface-name <em class="replaceable"><code>superVLAN</code></em></code>
+nmcli> <code class="command">set connection.interface-name <em class="replaceable"><code>superVLAN</code></em></code>
+nmcli> <code class="command">save</code>
+nmcli> <code class="command">quit</code></pre>
+
+ </div><div class="para">
+ The <span class="application"><strong>nmcli</strong></span> utility can be used to set and clear <code class="literal">ioctl</code> flags which change the way the 802.1Q code functions. The following VLAN flags are supported by <span class="application"><strong>NetworkManager</strong></span>:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 0x01 - reordering of output packet headers
+ </div></li><li class="listitem"><div class="para">
+ 0x02 - use GVRP protocol
+ </div></li><li class="listitem"><div class="para">
+ 0x04 - loose binding of the interface and its master
+ </div></li></ul></div>
+ The state of the VLAN is synchronized to the state of the parent or master interface (the interface or device on which the VLAN is created). If the parent interface is set to the <span class="quote">“<span class="quote">down</span>”</span> administrative state then all associated VLANs are set down and all routes are flushed from the routing table. Flag <code class="literal">0x04</code> enables a <em class="firstterm">loose binding</em> mode, in which only the operational state is passed from the parent to the associated VLANs, but the VLAN device state is not changed.
+ </div><div class="para">
+ To set a VLAN flag, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection modify vlan-VLAN10 vlan.flags 1</code></pre>
+
+ </div><div class="para">
+ See <a class="xref" href="#sec-Using_the_NetworkManager_Command_Line_Tool_nmcli">Section 2.4, “Using the NetworkManager Command Line Tool, nmcli”</a> for an introduction to <span class="application"><strong>nmcli</strong></span>.
+ </div></div><div class="section" id="sec-Configure_802_1Q_VLAN_Tagging-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.5. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding Network Teaming.
+ </div><div class="section" id="sec-Configure_802_1Q_VLAN_Tagging-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.5.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">ip-link(8)</code> man page — Describes the <span class="application"><strong>ip</strong></span> utility's network device configuration commands.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nmcli(1)</code> man page — Describes <span class="application"><strong>NetworkManager</strong></span>'s command‐line tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nmcli-examples(5)</code> man page — Gives examples of <span class="application"><strong>nmcli</strong></span> commands.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nm-settings(5)</code> man page — Description of settings and parameters of <span class="application"><strong>NetworkManager</strong></span> connections.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-Consistent_Network_Device_Naming" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 8. Consistent Network Device Naming</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sec-Naming_Schemes_Hierarchy">8.1. Naming Schemes Hierarchy</a></span></dt><dt><span class="section"><a href="#sec-Understanding_the_Device_Renaming_Procedure">8.2. Understanding the Device Renaming Procedure</a></span></dt><dt><span class="section"><a href="#sec-Understanding_the_Predictable_Network_Interface_Device_Names">8.3. Understanding the Predictable Network Interface Device Names</a></span></dt><dt><span class="section"><a href="#sec-Naming_Scheme_for_Network_Devices_Available_for_Linux_on_System_z">8.4. Naming Scheme for Network Devices Available for Linux on System z</a></span></dt><dt><span class="section"><a href="#sec-Naming_Scheme_for_VLAN_I
nterfaces">8.5. Naming Scheme for VLAN Interfaces</a></span></dt><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming_Using_biosdevname">8.6. Consistent Network Device Naming Using biosdevname</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming-System_Requirements">8.6.1. System Requirements</a></span></dt><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming-Enabling_and_Disabling">8.6.2. Enabling and Disabling the Feature</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming-Notes">8.7. Notes for Administrators</a></span></dt><dt><span class="section"><a href="#sec-Controlling_the_Selection_of_Network_Device_Names">8.8. Controlling the Selection of Network Device Names</a></span></dt><dt><span class="section"><a href="#sec-Disabling_Consistent_Network_Device_Naming">8.9. Disabling Consistent Network Device Naming</a></span></dt><dt><span class="sec
tion"><a href="#sec_Troubleshooting_Network_Device_Naming">8.10. Troubleshooting Network Device Naming</a></span></dt><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming-additional_resources">8.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Consistent_Network_Device_Naming-docs-inst">8.11.1. Installed Documentation</a></span></dt></dl></dd></dl></div><div class="para">
+ Fedora 20 provides methods for consistent and predictable network device naming for network interfaces. These features change the name of network interfaces on a system in order to make locating and differentiating the interfaces easier.
+ </div><div class="para">
+ Traditionally, network interfaces in Linux are enumerated as <code class="interfacename">eth[0123…]</code>, but these names do not necessarily correspond to actual labels on the chassis. Modern server platforms with multiple network adapters can encounter non-deterministic and counter-intuitive naming of these interfaces. This affects both network adapters embedded on the motherboard (<em class="firstterm">Lan-on-Motherboard</em>, or <em class="firstterm"><acronym class="acronym">LOM</acronym></em>) and add-in (single and multiport) adapters.
+ </div><div class="para">
+ In Fedora 20, <span class="application"><strong>udev</strong></span> supports a number of different naming schemes. The default is to assign fixed names based on firmware, topology, and location information. This has the advantage that the names are fully automatic, fully predictable, that they stay fixed even if hardware is added or removed (no re-enumeration takes place), and that broken hardware can be replaced seamlessly. The disadvantage is that they are sometimes harder to read than the <span class="interface">eth0</span> or <span class="interface">wlan0</span> names traditionally used. For example: <span class="interface">enp5s0</span>.
+ </div><div class="section" id="sec-Naming_Schemes_Hierarchy"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.1. Naming Schemes Hierarchy</h2></div></div></div><div class="para">
+ By default, <code class="systemitem">systemd</code> will name interfaces using the following policy to apply the supported naming schemes:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Scheme 1:</strong></span> Names incorporating Firmware or BIOS provided index numbers for on-board devices (example: <code class="literal">eno1</code>), are applied if that information from the firmware or BIOS is applicable and available, else falling back to scheme 2.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Scheme 2:</strong></span> Names incorporating Firmware or BIOS provided PCI Express hotplug slot index numbers (example: <code class="literal">ens1</code>) are applied if that information from the firmware or BIOS is applicable and available, else falling back to scheme 3.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Scheme 3:</strong></span> Names incorporating physical location of the connector of the hardware (example: <code class="literal">enp2s0</code>), are applied if applicable, else falling directly back to scheme 5 in all other cases.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Scheme 4:</strong></span> Names incorporating interface's MAC address (example: <code class="literal">enx78e7d1ea46da</code>), is not used by default, but is available if the user chooses.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Scheme 5:</strong></span> The traditional unpredictable kernel naming scheme, is used if all other methods fail (example: <code class="literal">eth0</code>).
+ </div></li></ul></div>
+ </div><div class="para">
+ This policy, the procedure outlined above, is the default. If the system has <span class="application"><strong>biosdevname</strong></span> enabled, it will be used. Note that enabling <span class="application"><strong>biosdevname</strong></span> requires passing <code class="command">biosdevname=1</code> as a command-line parameter except in the case of a Dell system, where <span class="application"><strong>biosdevname</strong></span> will be used by default as long as it is installed. If the user has added <span class="application"><strong>udev</strong></span> rules which change the name of the kernel devices, those rules will take precedence.
+ </div></div><div class="section" id="sec-Understanding_the_Device_Renaming_Procedure"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.2. Understanding the Device Renaming Procedure</h2></div></div></div><div class="para">
+ The device name procedure in detail is as follows:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ A rule in <code class="filename">/usr/lib/udev/rules.d/60-net.rules</code> instructs the <span class="application"><strong>udev</strong></span> helper utility, <span class="application"><strong>/lib/udev/rename_device</strong></span>, to look into all <code class="filename">/etc/sysconfig/network-scripts/ifcfg-<em class="replaceable"><code>suffix</code></em></code> files. If it finds an <code class="filename">ifcfg</code> file with a <code class="command">HWADDR</code> entry matching the MAC address of an interface it renames the interface to the name given in the <code class="filename">ifcfg</code> file by the <code class="command">DEVICE</code> directive.
+ </div></li><li class="step"><div class="para">
+ A rule in <code class="filename">/usr/lib/udev/rules.d/71-biosdevname.rules</code> instructs <span class="application"><strong>biosdevname</strong></span> to rename the interface according to its naming policy, provided that it was not renamed in a previous step, <span class="application"><strong>biosdevname</strong></span> is installed, and <code class="command">biosdevname=0</code> was not given as a kernel command on the boot command line.
+ </div></li><li class="step"><div class="para">
+ A rule in <code class="filename">/lib/udev/rules.d/75-net-description.rules</code> instructs <span class="application"><strong>udev</strong></span> to fill in the internal <span class="application"><strong>udev</strong></span> device property values ID_NET_NAME_ONBOARD, ID_NET_NAME_SLOT, ID_NET_NAME_PATH, ID_NET_NAME_MAC by examining the network interface device. Note, that some device properties might be undefined.
+ </div></li><li class="step"><div class="para">
+ A rule in <code class="filename">/usr/lib/udev/rules.d/80-net-name-slot.rules</code> instructs <span class="application"><strong>udev</strong></span> to rename the interface, provided that it was not renamed in step 1 or 2, and the kernel parameter <code class="command">net.ifnames=0</code> was not given, according to the following priority: ID_NET_NAME_ONBOARD, ID_NET_NAME_SLOT, ID_NET_NAME_PATH. It falls through to the next in the list, if one is unset. If none of these are set, then the interface will not be renamed.
+ </div></li></ol></div><div class="para">
+ Steps 3 and 4 are implementing the naming schemes 1, 2, 3, and optionally 4, described in <a class="xref" href="#sec-Naming_Schemes_Hierarchy">Section 8.1, “Naming Schemes Hierarchy”</a>. Step 2 is explained in more detail in <a class="xref" href="#sec-Consistent_Network_Device_Naming_Using_biosdevname">Section 8.6, “Consistent Network Device Naming Using biosdevname”</a>.
+ </div></div><div class="section" id="sec-Understanding_the_Predictable_Network_Interface_Device_Names"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.3. Understanding the Predictable Network Interface Device Names</h2></div></div></div><div class="para">
+ The names have two character prefixes based on the type of interface:
+ <div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <code class="literal">en</code> for Ethernet,
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">wl</code> for wireless LAN (WLAN),
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">ww</code> for wireless wide area network (WWAN).
+ </div></li></ol></div>
+
+ </div><div class="para">
+ The names have the following types:
+ <div class="table" id="Device_Name_Types"><h6>Table 8.1. Device Name Types</h6><div class="table-contents"><table summary="Device Name Types" border="1"><colgroup><col width="63%" class="Format" /><col width="38%" class="Description" /></colgroup><thead><tr><th class="">
+ Format
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ o<<em class="replaceable"><code>index</code></em>>
+ </td><td class="">
+ on-board device index number
+ </td></tr><tr><td class="">
+ s<<em class="replaceable"><code>slot></code></em>[f<<em class="replaceable"><code>function></code></em>][d<<em class="replaceable"><code>dev_id</code></em>>]
+ </td><td class="">
+ hotplug slot index number
+ </td></tr><tr><td class="">
+ x<<em class="replaceable"><code>MAC</code></em>>
+ </td><td class="">
+ MAC address
+ </td></tr><tr><td class="">
+ p<<em class="replaceable"><code>bus</code></em>>s<<em class="replaceable"><code>slot</code></em>>[f<<em class="replaceable"><code>function</code></em>>][d<<em class="replaceable"><code>dev_id</code></em>>]
+ </td><td class="">
+ PCI geographical location
+ </td></tr><tr><td class="">
+ p<<em class="replaceable"><code>bus</code></em>>s<<em class="replaceable"><code>slot</code></em>>[f<<em class="replaceable"><code>function</code></em>>][u<<em class="replaceable"><code>port</code></em>>][..][c<<em class="replaceable"><code>config</code></em>>][i<<em class="replaceable"><code>interface</code></em>>]
+ </td><td class="">
+ USB port number chain
+ </td></tr></tbody></table></div></div><br class="table-break" />
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ All multi-function PCI devices will carry the [f<<em class="replaceable"><code>function</code></em>>] number in the device name, including the function 0 device.
+ </div></li><li class="listitem"><div class="para">
+ For USB devices the full chain of port numbers of hubs is composed. If the name gets longer than the maximum number of 15 characters, the name is not exported.
+ </div></li><li class="listitem"><div class="para">
+ The USB configuration descriptors == 1 and USB interface descriptors == 0 values are suppressed (configuration == 1 and interface == 0 are the default values if only one USB configuration or interface exists).
+ </div></li></ul></div>
+
+ </div></div><div class="section" id="sec-Naming_Scheme_for_Network_Devices_Available_for_Linux_on_System_z"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.4. Naming Scheme for Network Devices Available for Linux on System z</h2></div></div></div><div class="para">
+ Use the bus-ID to create predictable device names for network interfaces in Linux on System z instances. The bus-ID identifies a device in the s390 channel subsystem. A bus ID identifies the device within the scope of a Linux instance. For a CCW device, the bus ID is the device's device number with a leading <code class="literal">0.n</code>, where <code class="literal">n</code> is the subchannel set ID. For example, <code class="literal">0.1.0ab1</code>.
+ </div><div class="para">
+ Network interfaces of device type Ethernet are named as follows: <pre class="synopsis">enccw<em class="replaceable"><code>0</code></em>.<em class="replaceable"><code>0</code></em>.<em class="replaceable"><code>1234</code></em></pre>
+ </div><div class="para">
+ CTC network devices of device type SLIP are named as follows: <pre class="synopsis">slccw<em class="replaceable"><code>0</code></em>.<em class="replaceable"><code>0</code></em>.<em class="replaceable"><code>1234</code></em></pre>
+ </div><div class="para">
+ Use the <code class="command">znetconf -c</code> command or the <code class="command">lscss -a</code> command to display available network devices and their bus-IDs.
+ </div><div class="table" id="Device_Name_Types_for_Linux_on_System_z"><h6>Table 8.2. Device Name Types for Linux on System z</h6><div class="table-contents"><table summary="Device Name Types for Linux on System z" border="1"><colgroup><col width="63%" class="Format" /><col width="38%" class="Description" /></colgroup><thead><tr><th class="">
+ Format
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ enccw<em class="replaceable"><code>bus-ID</code></em>
+ </td><td class="">
+ device type Ethernet
+ </td></tr><tr><td class="">
+ slccw<em class="replaceable"><code>bus-ID</code></em>
+ </td><td class="">
+ CTC network devices of device type SLIP
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sec-Naming_Scheme_for_VLAN_Interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.5. Naming Scheme for VLAN Interfaces</h2></div></div></div><div class="para">
+ Traditionally, VLAN interface names in the format: <em class="replaceable"><code>interface-name</code></em>.<em class="replaceable"><code>VLAN-ID</code></em> are used. The <code class="literal">VLAN-ID</code> ranges from <code class="literal">0</code> to <code class="literal">4096</code>, which is a maximum of four characters and the total interface name has a limit of 15 characters. The maximum interface name length is defined by the kernel headers and is a global limit, affecting all applications.
+ </div><div class="para">
+ In Fedora, four naming conventions for VLAN interface names are supported:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">VLAN plus VLAN ID </span></dt><dd><div class="para">
+ The word <code class="literal">vlan</code> plus the VLAN ID. For example: vlan0005
+ </div></dd><dt class="varlistentry"><span class="term">VLAN plus VLAN ID without padding</span></dt><dd><div class="para">
+ The word <code class="literal">vlan</code> plus the VLAN ID with out padding by means of an additional two zeros. For example: vlan5
+ </div></dd><dt class="varlistentry"><span class="term">Device name plus VLAN ID</span></dt><dd><div class="para">
+ The name of the parent interface plus the VLAN ID. For example: eth0.0005
+ </div></dd><dt class="varlistentry"><span class="term">Device name plus VLAN ID without padding</span></dt><dd><div class="para">
+ The name of the parent interface plus the VLAN ID with out padding by means of an additional two zeros. For example: eth0.05
+ </div></dd></dl></div></div><div class="section" id="sec-Consistent_Network_Device_Naming_Using_biosdevname"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.6. Consistent Network Device Naming Using biosdevname</h2></div></div></div><div class="para">
+ This feature, implemented via the <span class="application"><strong>biosdevname</strong></span> <span class="application"><strong>udev</strong></span> helper utility, will change the name of all embedded network interfaces, PCI card network interfaces, and virtual function network interfaces from the existing <code class="interfacename">eth[0123…]</code> to the new naming convention as shown in <a class="xref" href="#tabl-Consistent_Network_Device_Naming_biosdevname">Table 8.3, “The biosdevname Naming Convention”</a>. Note that unless the system is a Dell system, or <span class="application"><strong>biosdevname</strong></span> is explicitly enabled as described in <a class="xref" href="#sec-Consistent_Network_Device_Naming-Enabling_and_Disabling">Section 8.6.2, “Enabling and Disabling the Feature”</a>, the <code class="systemitem">systemd</code> naming scheme will take precedence.
+ </div><div class="table" id="tabl-Consistent_Network_Device_Naming_biosdevname"><h6>Table 8.3. The biosdevname Naming Convention</h6><div class="table-contents"><table summary="The biosdevname Naming Convention" border="1"><colgroup><col width="35%" class="device" /><col width="15%" class="old" /><col width="50%" class="new" /></colgroup><thead><tr><th class="">
+ Device
+ </th><th class="">
+ Old Name
+ </th><th class="">
+ New Name
+ </th></tr></thead><tbody><tr><td class="">
+ Embedded network interface (LOM)
+ </td><td class="">
+ <code class="interfacename">eth[0123…]</code>
+ </td><td class="">
+ <code class="interfacename">em[1234…]</code><a href="#ftn.idm225416969904" class="footnote"><sup class="footnote" id="idm225416969904">[a]</sup></a>
+ </td></tr><tr><td class="">
+ PCI card network interface
+ </td><td class="">
+ <code class="interfacename">eth[0123…]</code>
+ </td><td class="">
+ <code class="interfacename">p<<em class="replaceable"><code>slot</code></em>>p<<em class="replaceable"><code>ethernet port</code></em>></code><a href="#ftn.idm225463384224" class="footnote"><sup class="footnote" id="idm225463384224">[b]</sup></a>
+ </td></tr><tr><td class="">
+ Virtual function
+ </td><td class="">
+ <code class="interfacename">eth[0123…]</code>
+ </td><td class="">
+ <code class="interfacename">p<<em class="replaceable"><code>slot</code></em>>p<<em class="replaceable"><code>ethernet port</code></em>>_<<em class="replaceable"><code>virtual interface</code></em>></code><a href="#ftn.idm225480143824" class="footnote"><sup class="footnote" id="idm225480143824">[c]</sup></a>
+ </td></tr></tbody><tbody class="footnotes"><tr><td colspan="3"><div id="ftn.idm225416969904" class="footnote"><div class="para"><a href="#idm225416969904" class="para"><sup class="para">[a] </sup></a>
+ New enumeration starts at <code class="literal">1</code>.
+ </div></div><div id="ftn.idm225463384224" class="footnote"><div class="para"><a href="#idm225463384224" class="para"><sup class="para">[b] </sup></a>
+ For example: <code class="interfacename">p3p4</code>
+ </div></div><div id="ftn.idm225480143824" class="footnote"><div class="para"><a href="#idm225480143824" class="para"><sup class="para">[c] </sup></a>
+ For example: <code class="interfacename">p3p4_1</code>
+ </div></div></td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="sec-Consistent_Network_Device_Naming-System_Requirements"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.6.1. System Requirements</h3></div></div></div><div class="para">
+ The <span class="application"><strong>biosdevname</strong></span> program uses information from the system's BIOS, specifically the <span class="emphasis"><em>type 9</em></span> (System Slot) and <span class="emphasis"><em>type 41</em></span> (Onboard Devices Extended Information) fields contained within the SMBIOS. If the system's BIOS does not have SMBIOS version 2.6 or higher and this data, the new naming convention will not be used. Most older hardware does not support this feature because of a lack of BIOSes with the correct SMBIOS version and field information. For BIOS or SMBIOS version information, contact your hardware vendor.
+ </div><div class="para">
+ For this feature to take effect, the <span class="package">biosdevname</span> package must also be installed. To install it, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">yum install biosdevname</code></pre>
+
+ </div></div><div class="section" id="sec-Consistent_Network_Device_Naming-Enabling_and_Disabling"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.6.2. Enabling and Disabling the Feature</h3></div></div></div><div class="para">
+ To disable this feature, pass the following option on the boot command line, both during and after installation:
+ </div><pre class="screen"><code class="option">biosdevname=0</code></pre><div class="para">
+ To enable this feature, pass the following option on the boot command line, both during and after installation:
+ </div><pre class="screen"><code class="option">biosdevname=1</code></pre><div class="para">
+ Unless the system meets the minimum requirements, this option will be ignored and the system will use the <code class="systemitem">systemd</code> naming scheme as described in the beginning of the chapter.
+ </div><div class="para">
+ If the <code class="option">biosdevname</code> install option is specified, it must remain as a boot option for the lifetime of the system.
+ </div></div></div><div class="section" id="sec-Consistent_Network_Device_Naming-Notes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.7. Notes for Administrators</h2></div></div></div><div class="para">
+ Many system customization files can include network interface names, and thus will require updates if moving a system from the old convention to the new convention. If you use the new naming convention, you will also need to update network interface names in areas such as custom <span class="application"><strong>iptables</strong></span> rules, scripts altering <code class="systemitem">irqbalance</code>, and other similar configuration files. Also, enabling this change for installation will require modification to existing <span class="application"><strong>kickstart</strong></span> files that use device names via the <code class="option">ksdevice</code> parameter; these <span class="application"><strong>kickstart</strong></span> files will need to be updated to use the network device's MAC address or the network device's new name.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The maximum interface name length is defined by the kernel headers and is a global limit, affecting all applications.
+ </div></div></div></div><div class="section" id="sec-Controlling_the_Selection_of_Network_Device_Names"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.8. Controlling the Selection of Network Device Names</h2></div></div></div><div class="para">
+ Device naming can be controlled in the following manner:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">By identifying the network interface device</span></dt><dd><div class="para">
+ Setting the MAC address in an <code class="filename">ifcfg</code> file using the <code class="command">HWADDR</code> directive enables it to be identified by <span class="application"><strong>udev</strong></span>. The name will be taken from the string given by the <code class="command">DEVICE</code> directive, which by convention is the same as the <code class="filename">ifcfg</code> suffix. For example, <code class="filename">ifcfg</code>-<em class="replaceable"><code>eth0</code></em>.
+ </div></dd><dt class="varlistentry"><span class="term">By turning on or off <span class="application"><strong>biosdevname</strong></span></span></dt><dd><div class="para">
+ The name provided by <span class="application"><strong>biosdevname</strong></span> will be used (if <span class="application"><strong>biosdevname</strong></span> can determine one).
+ </div></dd><dt class="varlistentry"><span class="term">By turning on or off the <code class="systemitem">systemd-udev</code> naming scheme</span></dt><dd><div class="para">
+ The name provided by <code class="systemitem">systemd-udev</code> will be used (if <code class="systemitem">systemd-udev</code> can determine one).
+ </div></dd></dl></div></div><div class="section" id="sec-Disabling_Consistent_Network_Device_Naming"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.9. Disabling Consistent Network Device Naming</h2></div></div></div><div class="para">
+ To disable consistent network device naming, choose from one of the following:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Disable the assignment of fixed names, so that the unpredictable kernel names are used again, by masking <span class="application"><strong>udev</strong></span>'s rule file for the default policy. This <span class="quote">“<span class="quote">masking</span>”</span> can be done by making a symbolic link to <code class="filename">/dev/null</code>. As <code class="systemitem">root</code>, issue a command as follows:
+<pre class="screen">~]# <code class="command">ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules</code></pre>
+
+ </div></li><li class="listitem"><div class="para">
+ Create your own manual naming scheme, for example by naming your interfaces <span class="quote">“<span class="quote">internet0</span>”</span>, <span class="quote">“<span class="quote">dmz0</span>”</span> or <span class="quote">“<span class="quote">lan0</span>”</span>. To do that create your own <span class="application"><strong>udev</strong></span> rules file and set the NAME property for the devices. Make sure to order it before the default policy file, for example by naming it <code class="filename">/etc/udev/rules.d/70-my-net-names.rules</code>.
+ </div></li><li class="listitem"><div class="para">
+ Alter the default policy file to pick a different naming scheme, for example to name all interfaces after their MAC address by default. As <code class="systemitem">root</code> copy the default policy file as follows:
+<pre class="screen">~]# <code class="command">cp /usr/lib/udev/rules.d/80-net-name-slot.rules /etc/udev/rules.d/80-net-name-slot.rules</code></pre>
+ Edit the file in the <code class="filename">/etc/udev/rules.d/</code> directory and change the lines as necessary.
+ </div></li><li class="listitem"><div class="para">
+ Add the following line to the <code class="filename">/etc/default/grub</code> file: <pre class="synopsis">net.ifnames=0</pre> or pass it to the kernel at boot time using the GRUB2 command-line interface. For more information about GRUB2 see <em class="citetitle">Fedora 20 System Administrator's Guide</em>.
+ </div></li></ul></div>
+ </div></div><div class="section" id="sec_Troubleshooting_Network_Device_Naming"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.10. Troubleshooting Network Device Naming</h2></div></div></div><div class="para">
+ Predictable interface names will be assigned for each interface, if applicable, as per the procedure described in <a class="xref" href="#sec-Understanding_the_Device_Renaming_Procedure">Section 8.2, “Understanding the Device Renaming Procedure”</a>. To view the list of possible names <span class="application"><strong>udev</strong></span> will use, issue a command in the following form as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">udevadm info /sys/class/net/<em class="replaceable"><code>ifname</code></em> | grep ID_NET_NAME</code></pre>
+ where <em class="replaceable"><code>ifname</code></em> is one of the interfaces listed by the following command:
+<pre class="screen">~]$ <code class="command">ls /sys/class/net/</code></pre>
+
+ </div><div class="para">
+ One of the possible names will be applied by <span class="application"><strong>udev</strong></span> according to the rules as described in <a class="xref" href="#sec-Understanding_the_Device_Renaming_Procedure">Section 8.2, “Understanding the Device Renaming Procedure”</a>, and summarized here:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/lib/udev/rules.d/60-net.rules</code> - from initscripts,
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/lib/udev/rules.d/71-biosdevname.rules</code> - from <span class="application"><strong>biosdevname</strong></span>,
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/lib/udev/rules.d/80-net-name-slot.rules</code> - from <code class="systemitem">systemd</code>
+ </div></li></ul></div>
+
+ </div><div class="para">
+ From the above list of rule files it can be seen that if interface naming is done via initscripts or <span class="application"><strong>biosdevname</strong></span> it always takes precedence over <span class="application"><strong>udev</strong></span> native naming. However if initscripts renaming is not taking place and <span class="application"><strong>biosdevname</strong></span> is disabled, then to alter the interface names copy the <code class="filename">80-net-name-slot.rules</code> from <code class="filename">/usr/</code> to <code class="filename">/etc/</code> and edit the file appropriately. In other words, comment out or arrange schemes to be used in a certain order.
+ </div><div class="example" id="ex-Some_interfaces_have_names_from_the_kernel_namespace_while_others_are_successfully_renamed_by_udev"><h6>Example 8.1. Some interfaces have names from the kernel namespace (eth[0,1,2...]) while others are successfully renamed by udev</h6><div class="example-contents"><div class="para">
+ Mixed up schemes most likely means that either for some hardware there is no usable information provided by the kernel to <span class="application"><strong>udev</strong></span>, thus it could not figure out any names, or the information provided to <span class="application"><strong>udev</strong></span> is not suitable, for example non-unique device IDs. The latter is more common and the solution is to use a custom naming scheme in ifcfg files or alter which <span class="application"><strong>udev</strong></span> scheme is in use by editing 80-net-name-slot.rules.
+ </div></div></div><br class="example-break" /><div class="example" id="ex-In_var-log-messages_or_the_systemd_journal_renaming_is_seen_to_be_done_twice_for_each_interface"><h6>Example 8.2. In /var/log/messages or the systemd journal, renaming is seen to be done twice for each interface</h6><div class="example-contents"><div class="para">
+ Systems with the naming scheme encoded in ifcfg files but which do not have a regenerated <code class="systemitem">initrd</code> image are likely to encounter this issue. The interface name is initially assigned (via <span class="application"><strong>biosdevname</strong></span> or <span class="application"><strong>udev</strong></span> or dracut parameters on the kernel command line) during early-boot while still in <code class="systemitem">initrd</code>. Then after switching to real <code class="systemitem">rootfs</code>, renaming is done a second time and a new interface name is determined by the <code class="filename">/usr/lib/udev/rename_device</code> binary spawned by <span class="application"><strong>udev</strong></span> because of processing 60-net.rules. You can safely ignore such messages.
+ </div></div></div><br class="example-break" /><div class="example" id="ex-Using_naming_scheme_in_ifcfg_files_with_ethX_names_does_not_work"><h6>Example 8.3. Using naming scheme in ifcfg files with ethX names does not work</h6><div class="example-contents"><div class="para">
+ Use of interface names from kernel namespace is discouraged. To get predictable and stable interface names please use some other prefix than "eth".
+ </div></div></div><br class="example-break" /></div><div class="section" id="sec-Consistent_Network_Device_Naming-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.11. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding Network Teaming.
+ </div><div class="section" id="sec-Consistent_Network_Device_Naming-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.11.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">udev(7)</code> man page — Describes the Linux dynamic device management daemon, <code class="systemitem">udevd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">systemd(1)</code> man page — Describes <code class="systemitem">systemd</code> system and service manager.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">biosdevname(1)</code> man page — Describes the utility for obtaining the BIOS-given name of a device.
+ </div></li></ul></div></div></div></div></div><div class="part" id="part-Servers"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part II. Servers</h1></div></div></div><div class="partintro" id="idm225431715568"><div></div><div class="para">
+ This part discusses how to set up servers normally required for networking.
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#ch-DHCP_Servers">9. DHCP Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-dhcp-why">9.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="#sec-dhcp-configuring-server">9.2. Configuring a DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#config-file">9.2.1. Configuration File</a></span></dt><dt><span class="section"><a href="#lease-database">9.2.2. Lease Database</a></span></dt><dt><span class="section"><a href="#idm225408573744">9.2.3. Starting and Stopping the Server</a></span></dt></dl></dd><dt><span class="section"><a href="#dhcp-relay-agent">9.3. DHCP Relay Agent</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configure_dhcrelay_as_a_DHCPv4_and_BOOTP_relay_agent">9.3.1. Configure dhcrelay as a DHCPv4 and BOOTP relay agent</a></span></dt><dt><span class="section"><a href="#sec-Config
ure_dhcrelay_as_a_DHCPv6_relay_agent">9.3.2. Configure dhcrelay as a DHCPv6 relay agent</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_a_Multihomed_DHCP_Server">9.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-dns_Host_Configuration">9.4.1. Host Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-dhcp_for_ipv6_dhcpv6">9.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="#sec-dhcp-additional-resources">9.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-dhcp-installed-docs">9.6.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-DNS_Servers">10. DNS Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Introduction_to_DNS">10.1. Introduction to DNS</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-dns-introduction-zones">10.1.
1. Nameserver Zones</a></span></dt><dt><span class="section"><a href="#sec-dns-introduction-nameservers">10.1.2. Nameserver Types</a></span></dt><dt><span class="section"><a href="#sec-dns-introduction-bind">10.1.3. BIND as a Nameserver</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-BIND">10.2. BIND</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-bind-empty-zones">10.2.1. Empty Zones</a></span></dt><dt><span class="section"><a href="#sec-bind-namedconf">10.2.2. Configuring the named Service</a></span></dt><dt><span class="section"><a href="#sec-bind-zone">10.2.3. Editing Zone Files</a></span></dt><dt><span class="section"><a href="#sec-bind-rndc">10.2.4. Using the rndc Utility</a></span></dt><dt><span class="section"><a href="#sec-bind-dig">10.2.5. Using the dig Utility</a></span></dt><dt><span class="section"><a href="#sec-bind-features">10.2.6. Advanced Features of BIND</a></span></dt><dt><span class="section"><a href="#sec-bind-mistakes">1
0.2.7. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="#sec-bind-additional-resources">10.2.8. Additional Resources</a></span></dt></dl></dd></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" id="ch-DHCP_Servers" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 9. DHCP Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sec-dhcp-why">9.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="#sec-dhcp-configuring-server">9.2. Configuring a DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#config-file">9.2.1. Configuration File</a></span></dt><dt><span class="section"><a href="#lease-database">9.2.2. Lease Database</a></span></dt><dt><span class="section"><a href="#idm225408573744">9.2.3. Starting and Stopping the Server</a></span></dt></dl></dd><dt><span class="section"><a href="#dhcp-relay-agent">9.3. DHCP Relay Agent</a></span></dt
><dd><dl><dt><span class="section"><a href="#sec-Configure_dhcrelay_as_a_DHCPv4_and_BOOTP_relay_agent">9.3.1. Configure dhcrelay as a DHCPv4 and BOOTP relay agent</a></span></dt><dt><span class="section"><a href="#sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent">9.3.2. Configure dhcrelay as a DHCPv6 relay agent</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_a_Multihomed_DHCP_Server">9.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-dns_Host_Configuration">9.4.1. Host Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-dhcp_for_ipv6_dhcpv6">9.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="#sec-dhcp-additional-resources">9.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-dhcp-installed-docs">9.6.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="idm225434574576" class="indexterm"></a
><a id="idm225437346656" class="indexterm"></a><div class="para">
+ Dynamic Host Configuration Protocol (<acronym class="acronym">DHCP</acronym>) is a network protocol that automatically assigns TCP/IP information to client machines. Each <code class="systemitem">DHCP</code> client connects to the centrally located <code class="systemitem">DHCP</code> server, which returns the network configuration (including the <code class="systemitem">IP</code> address, gateway, and <code class="systemitem">DNS</code> servers) of that client.
+ </div><div class="section" id="sec-dhcp-why"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.1. Why Use DHCP?</h2></div></div></div><a id="idm225410890720" class="indexterm"></a><div class="para">
+ <code class="systemitem">DHCP</code> is useful for automatic configuration of client network interfaces. When configuring the client system, you can choose <code class="systemitem">DHCP</code> instead of specifying an <code class="systemitem">IP</code> address, netmask, gateway, or <code class="systemitem">DNS</code> servers. The client retrieves this information from the <code class="systemitem">DHCP</code> server. <code class="systemitem">DHCP</code> is also useful if you want to change the <code class="systemitem">IP</code> addresses of a large number of systems. Instead of reconfiguring all the systems, you can just edit one configuration file on the server for the new set of <code class="systemitem">IP</code> addresses. If the <code class="systemitem">DNS</code> servers for an organization changes, the changes happen on the <code class="systemitem">DHCP</code> server, not on the <code class="systemitem">DHCP</code> clients. When you restart the network or reboot the
clients, the changes go into effect.
+ </div><div class="para">
+ If an organization has a functional <code class="systemitem">DHCP</code> server correctly connected to a network, laptops and other mobile computer users can move these devices from office to office.
+ </div><div class="para">
+ Note that administrators of <code class="systemitem">DNS</code> and <code class="systemitem">DHCP</code> servers, as well as any provisioning applications, should agree on the host name format used in an organization. See <a class="xref" href="#sec-Recommended_Naming_Practices">Section 3.1.1, “Recommended Naming Practices”</a> for more information on the format of host names.
+ </div></div><div class="section" id="sec-dhcp-configuring-server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.2. Configuring a DHCP Server</h2></div></div></div><a id="idm225438474192" class="indexterm"></a><div class="para">
+ The <span class="package">dhcp</span> package contains an <em class="firstterm">Internet Systems Consortium</em> (<acronym class="acronym">ISC</acronym>) <code class="systemitem">DHCP</code> server. Install the package as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">yum install dhcp</code>
+</pre><div class="para">
+ Installing the <span class="package">dhcp</span> package creates a file, <code class="filename">/etc/dhcp/dhcpd.conf</code>, which is merely an empty configuration file. As <code class="systemitem">root</code>, issue the following command:
+ </div><pre class="programlisting">~]# <code class="command">cat /etc/dhcp/dhcpd.conf</code>
+#
+# DHCP Server Configuration file.
+# see /usr/share/doc/dhcp/dhcpd.conf.example
+# see dhcpd.conf(5) man page
+#</pre><div class="para">
+ The example configuration file can be found at <code class="filename">/usr/share/doc/dhcp/dhcpd.conf.example</code>. You should use this file to help you configure <code class="filename">/etc/dhcp/dhcpd.conf</code>, which is explained in detail below.
+ </div><div class="para">
+ <code class="systemitem">DHCP</code> also uses the file <code class="filename">/var/lib/dhcpd/dhcpd.leases</code> to store the client lease database. Refer to <a class="xref" href="#lease-database">Section 9.2.2, “Lease Database”</a> for more information.
+ </div><div class="section" id="config-file"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.1. Configuration File</h3></div></div></div><a id="idm225452673232" class="indexterm"></a><a id="idm225452671792" class="indexterm"></a><div class="para">
+ The first step in configuring a <code class="systemitem">DHCP</code> server is to create the configuration file that stores the network information for the clients. Use this file to declare options for client systems.
+ </div><div class="para">
+ The configuration file can contain extra tabs or blank lines for easier formatting. Keywords are case-insensitive and lines beginning with a hash sign (<code class="literal">#</code>) are considered comments.
+ </div><div class="para">
+ There are two types of statements in the configuration file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Parameters — State how to perform a task, whether to perform a task, or what network configuration options to send to the client.
+ </div></li><li class="listitem"><div class="para">
+ Declarations — Describe the topology of the network, describe the clients, provide addresses for the clients, or apply a group of parameters to a group of declarations.
+ </div></li></ul></div><a id="idm225458866896" class="indexterm"></a><div class="para">
+ The parameters that start with the keyword option are referred to as <em class="firstterm">options</em>. These options control <code class="systemitem">DHCP</code> options; whereas, parameters configure values that are not optional or control how the <code class="systemitem">DHCP</code> server behaves.
+ </div><a id="idm225486085408" class="indexterm"></a><div class="para">
+ Parameters (including options) declared before a section enclosed in curly brackets (<code class="literal">{ }</code>) are considered global parameters. Global parameters apply to all the sections below it.
+ </div><div class="important"><div class="admonition_header"><h2>Restart the DHCP Daemon for the Changes to Take Effect</h2></div><div class="admonition"><div class="para">
+ If the configuration file is changed, the changes do not take effect until the <code class="systemitem">DHCP</code> daemon is restarted with the command <code class="command">systemctl restart dhcpd</code>.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Use the omshell Command</h2></div><div class="admonition"><div class="para">
+ Instead of changing a <code class="systemitem">DHCP</code> configuration file and restarting the service each time, using the <code class="command">omshell</code> command provides an interactive way to connect to, query, and change the configuration of a <code class="systemitem">DHCP</code> server. By using <code class="command">omshell</code>, all changes can be made while the server is running. For more information on <code class="command">omshell</code>, see the <code class="command">omshell</code> man page.
+ </div></div></div><div class="para">
+ In <a class="xref" href="#subnet">Example 9.1, “Subnet Declaration”</a>, the <code class="command">routers</code>, <code class="command">subnet-mask</code>, <code class="command">domain-search</code>, <code class="command">domain-name-servers</code>, and <code class="command">time-offset</code> options are used for any <code class="command">host</code> statements declared below it.
+ </div><a id="idm225443876832" class="indexterm"></a><div class="para">
+ For every subnet which will be served, and for every subnet to which the <code class="systemitem">DHCP</code> server is connected, there must be one <code class="command">subnet</code> declaration, which tells the <code class="systemitem">DHCP</code> daemon how to recognize that an address is on that subnet. A <code class="command">subnet</code> declaration is required for each subnet even if no addresses will be dynamically allocated to that subnet.
+ </div><div class="para">
+ In this example, there are global options for every <code class="systemitem">DHCP</code> client in the subnet and a <code class="command">range</code> declared. Clients are assigned an <code class="systemitem">IP</code> address within the <code class="command">range</code>.
+ </div><div class="example" id="subnet"><h6>Example 9.1. Subnet Declaration</h6><div class="example-contents"><pre class="programlisting">subnet 192.168.1.0 netmask 255.255.255.0 {
+ option routers 192.168.1.254;
+ option subnet-mask 255.255.255.0;
+ option domain-search "example.com";
+ option domain-name-servers 192.168.1.1;
+ option time-offset -18000; # Eastern Standard Time
+ range 192.168.1.10 192.168.1.100;
+}</pre></div></div><br class="example-break" /><div class="para">
+ To configure a <code class="systemitem">DHCP</code> server that leases a dynamic <code class="systemitem">IP</code> address to a system within a subnet, modify the example values from <a class="xref" href="#dynamic-ip">Example 9.2, “Range Parameter”</a>. It declares a default lease time, maximum lease time, and network configuration values for the clients. This example assigns <code class="systemitem">IP</code> addresses in the <code class="command">range</code> <code class="systemitem">192.168.1.10</code> and <code class="systemitem">192.168.1.100</code> to client systems.
+ </div><div class="example" id="dynamic-ip"><h6>Example 9.2. Range Parameter</h6><div class="example-contents"><pre class="programlisting">default-lease-time 600;
+max-lease-time 7200;
+option subnet-mask 255.255.255.0;
+option broadcast-address 192.168.1.255;
+option routers 192.168.1.254;
+option domain-name-servers 192.168.1.1, 192.168.1.2;
+option domain-search "example.com";
+subnet 192.168.1.0 netmask 255.255.255.0 {
+ range 192.168.1.10 192.168.1.100;
+}</pre></div></div><br class="example-break" /><div class="para">
+ To assign an <code class="systemitem">IP</code> address to a client based on the MAC address of the network interface card, use the <code class="command">hardware ethernet</code> parameter within a <code class="command">host</code> declaration. As demonstrated in <a class="xref" href="#static-ip">Example 9.3, “Static IP Address Using DHCP”</a>, the <code class="command">host apex</code> declaration specifies that the network interface card with the MAC address <code class="systemitem">00:A0:78:8E:9E:AA</code> always receives the <code class="systemitem">IP</code> address <code class="systemitem">192.168.1.4</code>.
+ </div><div class="para">
+ Note that you can also use the optional parameter <code class="option">host-name</code> to assign a host name to the client.
+ </div><div class="example" id="static-ip"><h6>Example 9.3. Static IP Address Using DHCP</h6><div class="example-contents"><pre class="programlisting">host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}</pre></div></div><br class="example-break" /><a id="idm225457765616" class="indexterm"></a><div class="para">
+ All subnets that share the same physical network should be declared within a <code class="command">shared-network</code> declaration as shown in <a class="xref" href="#shared-network">Example 9.4, “Shared-network Declaration”</a>. Parameters within the <code class="command">shared-network</code>, but outside the enclosed subnet declarations, are considered to be global parameters. The name assigned to <code class="command">shared-network</code> must be a descriptive title for the network, such as using the title <span class="quote">“<span class="quote">test-lab</span>”</span> to describe all the subnets in a test lab environment.
+ </div><div class="example" id="shared-network"><h6>Example 9.4. Shared-network Declaration</h6><div class="example-contents"><pre class="programlisting">shared-network name {
+ option domain-search "test.redhat.com";
+ option domain-name-servers ns1.redhat.com, ns2.redhat.com;
+ option routers 192.168.0.254;
+ #more parameters for EXAMPLE shared-network
+ subnet 192.168.1.0 netmask 255.255.252.0 {
+ #parameters for subnet
+ range 192.168.1.1 192.168.1.254;
+ }
+ subnet 192.168.2.0 netmask 255.255.252.0 {
+ #parameters for subnet
+ range 192.168.2.1 192.168.2.254;
+ }
+}</pre></div></div><br class="example-break" /><a id="idm225425950720" class="indexterm"></a><div class="para">
+ As demonstrated in <a class="xref" href="#group">Example 9.5, “Group Declaration”</a>, the <code class="command">group</code> declaration is used to apply global parameters to a group of declarations. For example, shared networks, subnets, and hosts can be grouped.
+ </div><div class="example" id="group"><h6>Example 9.5. Group Declaration</h6><div class="example-contents"><pre class="programlisting">group {
+ option routers 192.168.1.254;
+ option subnet-mask 255.255.255.0;
+ option domain-search "example.com";
+ option domain-name-servers 192.168.1.1;
+ option time-offset -18000; # Eastern Standard Time
+ host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+ }
+ host raleigh {
+ option host-name "raleigh.example.com";
+ hardware ethernet 00:A1:DD:74:C3:F2;
+ fixed-address 192.168.1.6;
+ }
+}</pre></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Using the Example Configuration File</h2></div><div class="admonition"><div class="para">
+ You can use the provided example configuration file as a starting point and add custom configuration options to it. To copy this file to the proper location, use the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">cp /usr/share/doc/dhcp-<em class="replaceable"><code>version_number</code></em>/dhcpd.conf.example /etc/dhcp/dhcpd.conf</code></pre><div class="para">
+ ... where <em class="replaceable"><code>version_number</code></em> is the <code class="systemitem">DHCP</code> version number.
+ </div></div></div><div class="para">
+ For a complete list of option statements and what they do, see the <code class="filename">dhcp-options(5)</code> man page.
+ </div></div><div class="section" id="lease-database"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.2. Lease Database</h3></div></div></div><div class="para">
+ On the <code class="systemitem">DHCP</code> server, the file <code class="filename">/var/lib/dhcpd/dhcpd.leases</code> stores the <code class="systemitem">DHCP</code> client lease database. Do not change this file. <code class="systemitem">DHCP</code> lease information for each recently assigned <code class="systemitem">IP</code> address is automatically stored in the lease database. The information includes the length of the lease, to whom the <code class="systemitem">IP</code> address has been assigned, the start and end dates for the lease, and the MAC address of the network interface card that was used to retrieve the lease.
+ </div><div class="para">
+ All times in the lease database are in Coordinated Universal Time (UTC), not local time.
+ </div><div class="para">
+ The lease database is recreated from time to time so that it is not too large. First, all known leases are saved in a temporary lease database. The <code class="filename">dhcpd.leases</code> file is renamed <code class="filename">dhcpd.leases~</code> and the temporary lease database is written to <code class="filename">dhcpd.leases</code>.
+ </div><div class="para">
+ The <code class="systemitem">DHCP</code> daemon could be killed or the system could crash after the lease database has been renamed to the backup file but before the new file has been written. If this happens, the <code class="filename">dhcpd.leases</code> file does not exist, but it is required to start the service. Do not create a new lease file. If you do, all old leases are lost which causes many problems. The correct solution is to rename the <code class="filename">dhcpd.leases~</code> backup file to <code class="filename">dhcpd.leases</code> and then start the daemon.
+ </div></div><div class="section" id="idm225408573744"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225408573744">9.2.3. Starting and Stopping the Server</h3></div></div></div><a id="idm225408572976" class="indexterm"></a><a id="idm225457578064" class="indexterm"></a><a id="idm225457576624" class="indexterm"></a><a id="idm225457575024" class="indexterm"></a><div class="important"><div class="admonition_header"><h2>Starting the DHCP Server for the First Time</h2></div><div class="admonition"><div class="para">
+ When the <code class="systemitem">DHCP</code> server is started for the first time, it fails unless the <code class="filename">dhcpd.leases</code> file exists. You can use the command <code class="command">touch /var/lib/dhcpd/dhcpd.leases</code> to create the file if it does not exist. If the same server is also running BIND as a <code class="systemitem">DNS</code> server, this step is not necessary, as starting the <code class="command">named</code> service automatically checks for a <code class="filename">dhcpd.leases</code> file.
+ </div><div class="para">
+ Do not create a new lease file on a system that was previously running. If you do, all old leases are lost which causes many problems. The correct solution is to rename the <code class="filename">dhcpd.leases~</code> backup file to <code class="filename">dhcpd.leases</code> and then start the daemon.
+ </div></div></div><div class="para">
+ To start the <code class="systemitem">DHCP</code> service, use the following command:
+ </div><pre class="screen"><code class="command">systemctl start dhcpd.service</code></pre><div class="para">
+ To stop the <code class="systemitem">DHCP</code> server, type:
+ </div><pre class="screen"><code class="command">systemctl stop dhcpd.service</code></pre><div class="para">
+ By default, the <code class="systemitem">DHCP</code> service does not start at boot time. To configure the daemon to start automatically at boot time, run:
+ </div><pre class="screen"><code class="command">systemctl enable dhcpd.service</code></pre><div class="para">
+
+ </div><a id="idm225453321840" class="indexterm"></a><a id="idm225453320400" class="indexterm"></a><div class="para">
+ If more than one network interface is attached to the system, but the <code class="systemitem">DHCP</code> server should only listen for <code class="systemitem">DHCP</code> requests on one of the interfaces, configure the <code class="systemitem">DHCP</code> server to listen only on that device. The <code class="systemitem">DHCP</code> daemon will only listen on interfaces for which it finds a subnet declaration in the <code class="filename">/etc/dhcp/dhcpd.conf</code> file.
+ </div><div class="para">
+ This is useful for a firewall machine with two network cards. One network card can be configured as a <code class="systemitem">DHCP</code> client to retrieve an <code class="systemitem">IP</code> address to the Internet. The other network card can be used as a <code class="systemitem">DHCP</code> server for the internal network behind the firewall. Specifying only the network card connected to the internal network makes the system more secure because users can not connect to the daemon via the Internet.
+ </div><div class="para">
+ To specify command-line options, copy and then edit the <code class="filename">dhcpd.service</code> file as the <code class="systemitem">root</code> user. For example, as follows:
+<pre class="screen">~]# <code class="command">cp /usr/lib/systemd/system/dhcpd.service /etc/systemd/system/</code>
+~]# <code class="command">vi /etc/systemd/system/dhcpd.service</code></pre>
+ Edit the line under section [Service]: <pre class="synopsis">ExecStart=/usr/sbin/dhcpd -f -cf /etc/dhcp/dhcpd.conf -user dhcpd -group dhcpd --no-pid <em class="replaceable"><code>your_interface_name(s)</code></em></pre> Then, as the <code class="systemitem">root</code> user, restart the service:
+<pre class="screen">~]# <code class="command">systemctl --system daemon-reload</code>
+~]# <code class="command">systemctl restart dhcpd</code></pre>
+
+ </div><div class="para">
+ Command line options can be appended to <code class="command">ExecStart=/usr/sbin/dhcpd</code> in the <code class="filename">/etc/systemd/system/dhcpd.service</code> unit file under section [Service]. They include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-p <em class="replaceable"><code>portnum</code></em></code> — Specifies the UDP port number on which <code class="command">dhcpd</code> should listen. The default is port 67. The <code class="systemitem">DHCP</code> server transmits responses to the <code class="systemitem">DHCP</code> clients at a port number one greater than the UDP port specified. For example, if the default port 67 is used, the server listens on port 67 for requests and responds to the client on port 68. If a port is specified here and the <code class="systemitem">DHCP</code> relay agent is used, the same port on which the <code class="systemitem">DHCP</code> relay agent should listen must be specified. See <a class="xref" href="#dhcp-relay-agent">Section 9.3, “DHCP Relay Agent”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-f</code> — Runs the daemon as a foreground process. This is mostly used for debugging.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-d</code> — Logs the <code class="systemitem">DHCP</code> server daemon to the standard error descriptor. This is mostly used for debugging. If this is not specified, the log is written to <code class="filename">/var/log/messages</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-cf <em class="replaceable"><code>filename</code></em> </code> — Specifies the location of the configuration file. The default location is <code class="filename">/etc/dhcp/dhcpd.conf</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-lf <em class="replaceable"><code>filename</code></em> </code> — Specifies the location of the lease database file. If a lease database file already exists, it is very important that the same file be used every time the <code class="systemitem">DHCP</code> server is started. It is strongly recommended that this option only be used for debugging purposes on non-production machines. The default location is <code class="filename">/var/lib/dhcpd/dhcpd.leases</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-q</code> — Do not print the entire copyright message when starting the daemon.
+ </div></li></ul></div></div></div><div class="section" id="dhcp-relay-agent"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.3. DHCP Relay Agent</h2></div></div></div><a id="idm225446049824" class="indexterm"></a><a id="idm225446048384" class="indexterm"></a><a id="idm225446046944" class="indexterm"></a><div class="para">
+ The DHCP Relay Agent (<span class="application"><strong>dhcrelay</strong></span>) enables the relay of <code class="systemitem">DHCP</code> and <code class="systemitem">BOOTP</code> requests from a subnet with no <code class="systemitem">DHCP</code> server on it to one or more <code class="systemitem">DHCP</code> servers on other subnets.
+ </div><div class="para">
+ When a <code class="systemitem">DHCP</code> client requests information, the DHCP Relay Agent forwards the request to the list of <code class="systemitem">DHCP</code> servers specified when the DHCP Relay Agent is started. When a <code class="systemitem">DHCP</code> server returns a reply, the reply is broadcast or unicast on the network that sent the original request.
+ </div><div class="para">
+ The DHCP Relay Agent for <code class="systemitem">IPv4</code>, <span class="application"><strong>dhcrelay</strong></span>, listens for <code class="systemitem">DHCPv4</code> and <code class="systemitem">BOOTP</code> requests on all interfaces unless the interfaces are specified in <code class="filename">/etc/sysconfig/dhcrelay</code> with the <code class="computeroutput">INTERFACES</code> directive. See <a class="xref" href="#sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent">Section 9.3.2, “Configure dhcrelay as a DHCPv6 relay agent”</a>. The DHCP Relay Agent for <code class="systemitem">IPv6</code>, <span class="application"><strong>dhcrelay6</strong></span>, does not have this default behavior and interfaces to listen for <code class="systemitem">DHCPv6</code> requests must be specified. See <a class="xref" href="#sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent">Section 9.3.2, “Configure dhcrelay as a DHCPv6 relay agent”</a>.
+ </div><div class="para">
+ <span class="application"><strong>dhcrelay</strong></span> can either be run as a <code class="systemitem">DHCPv4</code> and <code class="systemitem">BOOTP</code> relay agent (by default) or as a <code class="systemitem">DHCPv6</code> relay agent (with <code class="option">-6</code> argument). To see the usage message, issue the command <code class="command">dhcrelay -h</code>.
+ </div><div class="section" id="sec-Configure_dhcrelay_as_a_DHCPv4_and_BOOTP_relay_agent"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.3.1. Configure dhcrelay as a DHCPv4 and BOOTP relay agent</h3></div></div></div><div class="para">
+ To run <span class="application"><strong>dhcrelay</strong></span> in <code class="systemitem">DHCPv4</code> and <code class="systemitem">BOOTP</code> mode specify the servers to which the requests should be forwarded to. Copy and then edit the <code class="filename">dhcrelay.service</code> file as the <code class="systemitem">root</code> user:
+<pre class="screen">~]# <code class="command">cp /lib/systemd/system/dhcrelay.service /etc/systemd/system/</code>
+~]# <code class="command">vi /etc/systemd/system/dhcrelay.service</code></pre>
+ </div><div class="para">
+ Edit the <code class="option">ExecStart</code> option under section [Service] and add one or more server <code class="systemitem">IPv4</code> addresses to the end of the line, for example: <pre class="synopsis">ExecStart=/usr/sbin/dhcrelay -d --no-pid 192.168.1.1</pre>
+ </div><div class="para">
+ If you also want to specify interfaces where the DHCP Relay Agent listens for <code class="systemitem">DHCP</code> requests, add them to the <code class="option">ExecStart</code> option with <code class="option">-i</code> argument (otherwise it will listen on all interfaces), for example: <pre class="synopsis">ExecStart=/usr/sbin/dhcrelay -d --no-pid 192.168.1.1 -i em1</pre> For other options see the <code class="filename">dhcrelay(8)</code> man page.
+ </div><div class="para">
+ To activate the changes made, as the <code class="systemitem">root</code> user, restart the service:
+<pre class="screen">~]# <code class="command">systemctl --system daemon-reload</code>
+~]# <code class="command">systemctl restart dhcrelay</code></pre>
+ </div></div><div class="section" id="sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.3.2. Configure dhcrelay as a DHCPv6 relay agent</h3></div></div></div><div class="para">
+ To run <span class="application"><strong>dhcrelay</strong></span> in <code class="systemitem">DHCPv6</code> mode add the <code class="option">-6</code> argument and specify the <span class="quote">“<span class="quote">lower interface</span>”</span> (on which queries will be received from clients or from other relay agents) and the <span class="quote">“<span class="quote">upper interface</span>”</span> (to which queries from clients and other relay agents should be forwarded). Copy <code class="filename">dhcrelay.service</code> to <code class="filename">dhcrelay6.service</code> and edit it as the <code class="systemitem">root</code> user:
+<pre class="screen">~]# <code class="command">cp /lib/systemd/system/dhcrelay.service /etc/systemd/system/dhcrelay6.service</code>
+~]# <code class="command">vi /etc/systemd/system/dhcrelay6.service</code></pre>
+ </div><div class="para">
+ Edit the <code class="option">ExecStart</code> option under section [Service] add <code class="option">-6</code> argument and add the <span class="quote">“<span class="quote">lower interface</span>”</span> and <span class="quote">“<span class="quote">upper interface</span>”</span> interface, for example: <pre class="synopsis">ExecStart=/usr/sbin/dhcrelay -d --no-pid -6 -l em1 -u em2</pre> For other options see the <code class="filename">dhcrelay(8)</code> man page.
+ </div><div class="para">
+ To activate the changes made, as the <code class="systemitem">root</code> user, restart the service:
+<pre class="screen">~]# <code class="command">systemctl --system daemon-reload</code>
+~]# <code class="command">systemctl restart dhcrelay6</code></pre>
+ </div></div></div><div class="section" id="sec-Configuring_a_Multihomed_DHCP_Server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.4. Configuring a Multihomed DHCP Server</h2></div></div></div><a id="idm225487081008" class="indexterm"></a><div class="para">
+ A multihomed <code class="systemitem">DHCP</code> server serves multiple networks, that is, multiple subnets. The examples in these sections detail how to configure a <code class="systemitem">DHCP</code> server to serve multiple networks, select which network interfaces to listen on, and how to define network settings for systems that move networks.
+ </div><div class="para">
+ Before making any changes, back up the existing <code class="filename">/etc/dhcp/dhcpd.conf</code> file.
+ </div><div class="para">
+ The <code class="systemitem">DHCP</code> daemon will only listen on interfaces for which it finds a subnet declaration in the <code class="filename">/etc/dhcp/dhcpd.conf</code> file.
+ </div><div class="para">
+ The following is a basic <code class="filename">/etc/dhcp/dhcpd.conf</code> file, for a server that has two network interfaces, <span class="interface">eth0</span> in a <code class="systemitem">10.0.0.0/24</code> network, and <span class="interface">eth1</span> in a <code class="systemitem">172.16.0.0/24</code> network. Multiple <code class="computeroutput">subnet</code> declarations allow you to define different settings for multiple networks:
+ </div><pre class="programlisting">default-lease-time <em class="replaceable"><code>600</code></em>;
+max-lease-time <em class="replaceable"><code>7200</code></em>;
+subnet 10.0.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 10.0.0.1;
+ range 10.0.0.5 10.0.0.15;
+}
+subnet 172.16.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 172.16.0.1;
+ range 172.16.0.5 172.16.0.15;
+}</pre><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="computeroutput">subnet <em class="replaceable"><code>10.0.0.0</code></em> netmask <em class="replaceable"><code>255.255.255.0</code></em>;</code> </span></dt><dd><div class="para">
+ A <code class="computeroutput">subnet</code> declaration is required for every network your <code class="systemitem">DHCP</code> server is serving. Multiple subnets require multiple <code class="computeroutput">subnet</code> declarations. If the <code class="systemitem">DHCP</code> server does not have a network interface in a range of a <code class="computeroutput">subnet</code> declaration, the <code class="systemitem">DHCP</code> server does not serve that network.
+ </div><div class="para">
+ If there is only one <code class="computeroutput">subnet</code> declaration, and no network interfaces are in the range of that subnet, the <code class="systemitem">DHCP</code> daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="programlisting">dhcpd: No subnet declaration for eth0 (0.0.0.0).
+dhcpd: ** Ignoring requests on eth0. If this is not what
+dhcpd: you want, please write a subnet declaration
+dhcpd: in your dhcpd.conf file for the network segment
+dhcpd: to which interface eth1 is attached. **
+dhcpd:
+dhcpd:
+dhcpd: Not configured to listen on any interfaces!</pre></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">option subnet-mask <em class="replaceable"><code>255.255.255.0</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">option subnet-mask</code> option defines a subnet mask, and overrides the <code class="computeroutput">netmask</code> value in the <code class="computeroutput">subnet</code> declaration. In simple cases, the subnet and netmask values are the same.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">option routers <em class="replaceable"><code>10.0.0.1</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">option routers</code> option defines the default gateway for the subnet. This is required for systems to reach internal networks on a different subnet, as well as external networks.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">range <em class="replaceable"><code>10.0.0.5</code></em> <em class="replaceable"><code>10.0.0.15</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">range</code> option specifies the pool of available <code class="systemitem">IP</code> addresses. Systems are assigned an address from the range of specified <code class="systemitem">IP</code> addresses.
+ </div></dd></dl></div><div class="para">
+ For further information, see the <code class="filename">dhcpd.conf(5)</code> man page.
+ </div><div class="section" id="sec-dns_Host_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.4.1. Host Configuration</h3></div></div></div><a id="idm225437586080" class="indexterm"></a><div class="para">
+ Before making any changes, back up the existing <code class="filename">/etc/sysconfig/dhcpd</code> and <code class="filename">/etc/dhcp/dhcpd.conf</code> files.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm225437583232">Configuring a Single System for Multiple Networks</h5>
+ The following <code class="filename">/etc/dhcp/dhcpd.conf</code> example creates two subnets, and configures an <code class="systemitem">IP</code> address for the same system, depending on which network it connects to:
+ </div><pre class="programlisting">default-lease-time <em class="replaceable"><code>600</code></em>;
+max-lease-time <em class="replaceable"><code>7200</code></em>;
+subnet 10.0.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 10.0.0.1;
+ range 10.0.0.5 10.0.0.15;
+}
+subnet 172.16.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 172.16.0.1;
+ range 172.16.0.5 172.16.0.15;
+}
+host example0 {
+ hardware ethernet 00:1A:6B:6A:2E:0B;
+ fixed-address 10.0.0.20;
+}
+host example1 {
+ hardware ethernet 00:1A:6B:6A:2E:0B;
+ fixed-address 172.16.0.20;
+}</pre><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="computeroutput">host <em class="replaceable"><code>example0</code></em> </code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">host</code> declaration defines specific parameters for a single system, such as an <code class="systemitem">IP</code> address. To configure specific parameters for multiple hosts, use multiple <code class="computeroutput">host</code> declarations.
+ </div><div class="para">
+ Most <code class="systemitem">DHCP</code> clients ignore the name in <code class="computeroutput">host</code> declarations, and as such, this name can be anything, as long as it is unique to other <code class="computeroutput">host</code> declarations. To configure the same system for multiple networks, use a different name for each <code class="computeroutput">host</code> declaration, otherwise the <code class="systemitem">DHCP</code> daemon fails to start. Systems are identified by the <code class="computeroutput">hardware ethernet</code> option, not the name in the <code class="computeroutput">host</code> declaration.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">hardware ethernet <em class="replaceable"><code>00:1A:6B:6A:2E:0B</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">hardware ethernet</code> option identifies the system. To find this address, run the <code class="command">ip link</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">fixed-address <em class="replaceable"><code>10.0.0.20</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">fixed-address</code> option assigns a valid <code class="systemitem">IP</code> address to the system specified by the <code class="computeroutput">hardware ethernet</code> option. This address must be outside the <code class="systemitem">IP</code> address pool specified with the <code class="computeroutput">range</code> option.
+ </div></dd></dl></div><div class="para">
+ If <code class="computeroutput">option</code> statements do not end with a semicolon, the <code class="systemitem">DHCP</code> daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="programlisting">/etc/dhcp/dhcpd.conf line 20: semicolon expected.
+dhcpd: }
+dhcpd: ^
+dhcpd: /etc/dhcp/dhcpd.conf line 38: unexpected end of file
+dhcpd:
+dhcpd: ^
+dhcpd: Configuration file errors encountered -- exiting</pre><div class="formalpara"><h5 class="formalpara" id="idm225483857136">Configuring Systems with Multiple Network Interfaces</h5>
+ The following <code class="computeroutput">host</code> declarations configure a single system, which has multiple network interfaces, so that each interface receives the same <code class="systemitem">IP</code> address. This configuration will not work if both network interfaces are connected to the same network at the same time:
+ </div><pre class="programlisting">host interface0 {
+ hardware ethernet 00:1a:6b:6a:2e:0b;
+ fixed-address 10.0.0.18;
+}
+host interface1 {
+ hardware ethernet 00:1A:6B:6A:27:3A;
+ fixed-address 10.0.0.18;
+}</pre><div class="para">
+ For this example, <code class="computeroutput">interface0</code> is the first network interface, and <code class="computeroutput">interface1</code> is the second interface. The different <code class="computeroutput">hardware ethernet</code> options identify each interface.
+ </div><div class="para">
+ If such a system connects to another network, add more <code class="computeroutput">host</code> declarations, remembering to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ assign a valid <code class="computeroutput">fixed-address</code> for the network the host is connecting to.
+ </div></li><li class="listitem"><div class="para">
+ make the name in the <code class="computeroutput">host</code> declaration unique.
+ </div></li></ul></div><div class="para">
+ When a name given in a <code class="computeroutput">host</code> declaration is not unique, the <code class="systemitem">DHCP</code> daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="programlisting">dhcpd: /etc/dhcp/dhcpd.conf line 31: host interface0: already exists
+dhcpd: }
+dhcpd: ^
+dhcpd: Configuration file errors encountered -- exiting</pre><div class="para">
+ This error was caused by having multiple <code class="computeroutput">host interface0</code> declarations defined in <code class="filename">/etc/dhcp/dhcpd.conf</code>.
+ </div></div></div><div class="section" id="sec-dhcp_for_ipv6_dhcpv6"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.5. DHCP for IPv6 (DHCPv6)</h2></div></div></div><a id="idm225440679152" class="indexterm"></a><a id="idm225440677712" class="indexterm"></a><div class="para">
+ The ISC <code class="systemitem">DHCP</code> includes support for <code class="systemitem">IPv6</code> (<code class="systemitem">DHCPv6</code>) since the 4.x release with a <code class="systemitem">DHCPv6</code> server, client, and relay agent functionality. The agents support both <code class="systemitem">IPv4</code> and <code class="systemitem">IPv6</code>, however the agents can only manage one protocol at a time; for dual support they must be started separately for <code class="systemitem">IPv4</code> and <code class="systemitem">IPv6</code>. For example, configure both <code class="systemitem">DHCPv4</code> and <code class="systemitem">DHCPv6</code> by editing their respective configuration files <code class="filename">/etc/dhcp/dhcpd.conf</code> and <code class="filename">/etc/dhcp/dhcpd6.conf</code> and then issue the following commands:
+<pre class="screen">~]# <code class="command">systemctl start dhcpd</code>
+~]# <code class="command">systemctl start dhcpd6</code></pre>
+
+ </div><div class="para">
+ The <code class="systemitem">DHCPv6</code> server configuration file can be found at <code class="filename">/etc/dhcp/dhcpd6.conf</code>.
+ </div><div class="para">
+ The example server configuration file can be found at <code class="filename">/usr/share/doc/dhcp/dhcpd6.conf.example</code>.
+ </div><div class="para">
+ A simple <code class="systemitem">DHCPv6</code> server configuration file can look like this:
+ </div><pre class="programlisting">subnet6 2001:db8:0:1::/64 {
+ range6 2001:db8:0:1::129 2001:db8:0:1::254;
+ option dhcp6.name-servers fec0:0:0:1::1;
+ option dhcp6.domain-search "domain.example";
+}</pre></div><div class="section" id="sec-dhcp-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.6. Additional Resources</h2></div></div></div><a id="idm225465534112" class="indexterm"></a><div class="para">
+ For additional information, see <em class="citetitle">The DHCP Handbook; Ralph Droms and Ted Lemon; 2003</em> or the following resources.
+ </div><div class="section" id="sec-dhcp-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.6.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">dhcpd(8)</code> man page — Describes how the <code class="systemitem">DHCP</code> daemon works.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcpd.conf(5)</code> man page — Explains how to configure the <code class="systemitem">DHCP</code> configuration file; includes some examples.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcpd.leases(5)</code> man page — Describes a persistent database of leases.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcp-options(5)</code> man page — Explains the syntax for declaring <code class="systemitem">DHCP</code> options in <code class="filename">dhcpd.conf</code>; includes some examples.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcrelay(8)</code> man page — Explains the <code class="systemitem">DHCP</code> Relay Agent and its configuration options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/dhcp/</code> — Contains example configuration files.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/dhcp-common/</code> — Contains README files, and release notes for current versions of the <code class="systemitem">DHCP</code> service.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-DNS_Servers" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 10. DNS Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sec-Introduction_to_DNS">10.1. Introduction to DNS</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-dns-introduction-zones">10.1.1. Nameserver Zones</a></span></dt><dt><span class="section"><a href="#sec-dns-introduction-nameservers">10.1.2. Nameserver Types</a></span></dt><dt><span class="section"><a href="#sec-dns-introduction-bind">10.1.3. BIND as a Nameserver</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-BIND">10.2. BIND</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-bind-empty-zones">10.2.1. Empty Zones</a></span></dt><dt><span class="section"><a href="#sec-bind-namedconf">10.2.2. Configuring the named Service</a></span></dt><dt><span class="s
ection"><a href="#sec-bind-zone">10.2.3. Editing Zone Files</a></span></dt><dt><span class="section"><a href="#sec-bind-rndc">10.2.4. Using the rndc Utility</a></span></dt><dt><span class="section"><a href="#sec-bind-dig">10.2.5. Using the dig Utility</a></span></dt><dt><span class="section"><a href="#sec-bind-features">10.2.6. Advanced Features of BIND</a></span></dt><dt><span class="section"><a href="#sec-bind-mistakes">10.2.7. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="#sec-bind-additional-resources">10.2.8. Additional Resources</a></span></dt></dl></dd></dl></div><a id="idm225489129456" class="indexterm"></a><a id="idm225489537312" class="indexterm"></a><div class="para">
+ <code class="systemitem">DNS</code> (Domain Name System), is a distributed database system that is used to associate host names with their respective <code class="systemitem">IP</code> addresses. For users, this has the advantage that they can refer to machines on the network by names that are usually easier to remember than the numerical network addresses. For system administrators, using a <code class="systemitem">DNS</code> server, also known as a <em class="firstterm">nameserver</em>, enables changing the <code class="systemitem">IP</code> address for a host without ever affecting the name-based queries. The use of the <code class="systemitem">DNS</code> databases is not only for resolving <code class="systemitem">IP</code> addresses to domain names and their use is becoming broader and broader as DNSSEC is deployed.
+ </div><div class="section" id="sec-Introduction_to_DNS"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.1. Introduction to DNS</h2></div></div></div><a id="idm225489131184" class="indexterm"></a><div class="para">
+ <code class="systemitem">DNS</code> is usually implemented using one or more centralized servers that are authoritative for certain domains. When a client host requests information from a nameserver, it usually connects to port 53. The nameserver then attempts to resolve the name requested. If the nameserver is configured to be a recursive name servers and it does not have an authoritative answer, or does not already have the answer cached from an earlier query, it queries other nameservers, called <em class="firstterm">root nameservers</em>, to determine which nameservers are authoritative for the name in question, and then queries them to get the requested name. Nameservers configured as purely authoritative, with recursion disabled, will not do lookups on behalf of clients.
+ </div><div class="section" id="sec-dns-introduction-zones"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.1.1. Nameserver Zones</h3></div></div></div><a id="idm225489134976" class="indexterm"></a><a id="idm225434136480" class="indexterm"></a><div class="para">
+ In a <code class="systemitem">DNS</code> server, all information is stored in basic data elements called <em class="firstterm">resource records</em> (<acronym class="acronym">RR</acronym>). Resource records are defined in <a href="http://www.rfc-editor.org/rfc/rfc1034.txt">RFC 1034</a>. The domain names are organized into a tree structure. Each level of the hierarchy is divided by a period (<code class="literal">.</code>). For example: The root domain, denoted by <code class="literal">.</code>, is the root of the <code class="systemitem">DNS</code> tree, which is at level zero. The domain name <code class="systemitem">com</code>, referred to as the <em class="firstterm">top-level domain</em> (<acronym class="acronym">TLD</acronym>) is a child of the root domain (<code class="literal">.</code>) so it is the first level of the hierarchy. The domain name <code class="systemitem">example.com</code> is at the second level of the hierarchy.
+ </div><div class="example" id="example-dns-introduction-zones-rr"><h6>Example 10.1. A Simple Resource Record</h6><div class="example-contents"><div class="para">
+ An example of a simple <em class="firstterm">resource record</em> (<acronym class="acronym">RR</acronym>):
+ </div><pre class="screen">example.com. 86400 IN A 192.0.2.1</pre><div class="para">
+ The domain name, <code class="systemitem">example.com</code>, is the <em class="firstterm">owner</em> for the RR. The value <code class="literal">86400</code> is the <em class="firstterm">time to live</em> (<acronym class="acronym">TTL</acronym>). The letters <code class="literal">IN</code>, meaning <span class="quote">“<span class="quote">the Internet system</span>”</span>, indicate the <em class="firstterm">class</em> of the RR. The letter <code class="literal">A</code> indicates the <em class="firstterm">type</em> of RR (in this example, a host address). The host address <code class="systemitem">192.0.2.1</code> is the data contained in the final section of this RR. This one line example is a RR. A set of RRs with the same type, owner, and class is called a <em class="firstterm">resource record set</em> (<acronym class="acronym">RRSet</acronym>).
+ </div></div></div><br class="example-break" /><a id="idm225487508880" class="indexterm"></a><a id="idm225487511312" class="indexterm"></a><a id="idm225487513696" class="indexterm"></a><div class="para">
+ Zones are defined on authoritative nameservers through the use of <em class="firstterm">zone files</em>, which contain definitions of the resource records in each zone. Zone files are stored on <em class="firstterm">primary nameservers</em> (also called <em class="firstterm">master nameservers</em>), where changes are made to the files, and <em class="firstterm">secondary nameservers</em> (also called <em class="firstterm">slave nameservers</em>), which receive zone definitions from the primary nameservers. Both primary and secondary nameservers are authoritative for the zone and look the same to clients. Depending on the configuration, any nameserver can also serve as a primary or secondary server for multiple zones at the same time.
+ </div><div class="para">
+ Note that administrators of <code class="systemitem">DNS</code> and <code class="systemitem">DHCP</code> servers, as well as any provisioning applications, should agree on the host name format used in an organization. See <a class="xref" href="#sec-Recommended_Naming_Practices">Section 3.1.1, “Recommended Naming Practices”</a> for more information on the format of host names.
+ </div></div><div class="section" id="sec-dns-introduction-nameservers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.1.2. Nameserver Types</h3></div></div></div><div class="para">
+ There are two nameserver configuration types:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225463722224" class="indexterm"></a>
+ <a id="idm225463725056" class="indexterm"></a>
+ <a id="idm225463727280" class="indexterm"></a>
+ <a id="idm225439543824" class="indexterm"></a>
+ <a id="idm225439545232" class="indexterm"></a>
+ <a id="idm225439547440" class="indexterm"></a>
+ authoritative </span></dt><dd><div class="para">
+ Authoritative nameservers answer to resource records that are part of their zones only. This category includes both primary (master) and secondary (slave) nameservers.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225439550848" class="indexterm"></a>
+ <a id="idm225488084416" class="indexterm"></a>
+ recursive </span></dt><dd><div class="para">
+ Recursive nameservers offer resolution services, but they are not authoritative for any zone. Answers for all resolutions are cached in a memory for a fixed period of time, which is specified by the retrieved resource record.
+ </div></dd></dl></div><div class="para">
+ Although a nameserver can be both authoritative and recursive at the same time, it is recommended not to combine the configuration types. To be able to perform their work, authoritative servers should be available to all clients all the time. On the other hand, since the recursive lookup takes far more time than authoritative responses, recursive servers should be available to a restricted number of clients only, otherwise they are prone to distributed denial of service (DDoS) attacks.
+ </div></div><div class="section" id="sec-dns-introduction-bind"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.1.3. BIND as a Nameserver</h3></div></div></div><a id="idm225488089024" class="indexterm"></a><a id="idm225422224848" class="indexterm"></a><a id="idm225422227200" class="indexterm"></a><a id="idm225422229920" class="indexterm"></a><a id="idm225422231440" class="indexterm"></a><a id="idm225443637232" class="indexterm"></a><div class="para">
+ BIND consists of a set of DNS-related programs. It contains a nameserver called <code class="systemitem">named</code>, an administration utility called <code class="command">rndc</code>, and a debugging tool called <code class="command">dig</code>. See <em class="citetitle">Fedora 20 System Administrator's Guide</em> for more information on how to run a service in Fedora.
+ </div></div></div><div xml:lang="en-US" class="section" id="sec-BIND" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.2. BIND</h2></div></div></div><a id="idm225443643264" class="indexterm"></a><div class="para">
+ This section covers <code class="systemitem">BIND</code> (Berkeley Internet Name Domain), the <code class="systemitem">DNS</code> server included in Fedora. It focuses on the structure of its configuration files, and describes how to administer it both locally and remotely.
+ </div><div class="section" id="sec-bind-empty-zones"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.1. Empty Zones</h3></div></div></div><div class="para">
+ <code class="systemitem">BIND</code> configures a number of <span class="quote">“<span class="quote">empty zones</span>”</span> to prevent recursive servers from sending unnecessary queries to Internet servers that cannot handle them (thus creating delays and SERVFAIL responses to clients who query for them). These empty zones ensure that immediate and authoritative NXDOMAIN responses are returned instead. The configuration option <code class="command">empty-zones-enable</code> controls whether or not empty zones are created, whilst the option <code class="command">disable-empty-zone</code> can be used in addition to disable one or more empty zones from the list of default prefixes that would be used.
+ </div><div class="para">
+ The number of empty zones created for <a href="http://www.rfc-editor.org/info/rfc1918"><em class="citetitle">RFC 1918</em></a> prefixes has been increased, and users of <code class="systemitem">BIND 9.9</code> and above will see the <a href="http://www.rfc-editor.org/info/rfc1918"><em class="citetitle">RFC 1918</em></a> empty zones both when <code class="command">empty-zones-enable</code> is unspecified (defaults to <code class="literal">yes</code>), and when it is explicitly set to <code class="literal">yes</code>.
+ </div></div><div class="section" id="sec-bind-namedconf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.2. Configuring the named Service</h3></div></div></div><a id="idm225464361104" class="indexterm"></a><div class="para">
+ When the <code class="systemitem">named</code> service is started, it reads the configuration from the files as described in <a class="xref" href="#table-bind-namedconf-files">Table 10.1, “The named Service Configuration Files”</a>.
+ </div><a id="idm225436237168" class="indexterm"></a><a id="idm225436239936" class="indexterm"></a><a id="idm225436241056" class="indexterm"></a><div class="table" id="table-bind-namedconf-files"><h6>Table 10.1. The named Service Configuration Files</h6><div class="table-contents"><table summary="The named Service Configuration Files" border="1"><colgroup><col width="38%" class="path" /><col width="63%" class="description" /></colgroup><thead><tr><th class="">
+ Path
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="filename">/etc/named.conf</code>
+ </td><td class="">
+ The main configuration file.
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/named/</code>
+ </td><td class="">
+ An auxiliary directory for configuration files that are included in the main configuration file.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The configuration file consists of a collection of statements with nested options surrounded by opening and closing curly brackets (<code class="literal">{</code> and <code class="literal">}</code>). Note that when editing the file, you have to be careful not to make any syntax error, otherwise the <code class="systemitem">named</code> service will not start. A typical <code class="filename">/etc/named.conf</code> file is organized as follows:
+ </div><pre class="programlisting"><em class="replaceable"><code>statement-1</code></em> ["<em class="replaceable"><code>statement-1-name</code></em>"] [<em class="replaceable"><code>statement-1-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};
+<em class="replaceable"><code>statement-2</code></em> ["<em class="replaceable"><code>statement-2-name</code></em>"] [<em class="replaceable"><code>statement-2-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};
+<em class="replaceable"><code>statement-N</code></em> ["<em class="replaceable"><code>statement-N-name</code></em>"] [<em class="replaceable"><code>statement-N-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};</pre><div class="note"><div class="admonition_header"><h2>Running BIND in a chroot environment</h2></div><div class="admonition"><div class="para">
+ If you have installed the <span class="package">bind-chroot</span> package, the BIND service will run in the <code class="command">chroot</code> environment. In that case, the initialization script will mount the above configuration files using the <code class="command">mount --bind</code> command, so that you can manage the configuration outside this environment. There is no need to copy anything into the <code class="filename">/var/named/chroot/</code> directory because it is mounted automatically. This simplifies maintenance since you do not need to take any special care of <code class="systemitem">BIND</code> configuration files if it is run in a <code class="command">chroot</code> environment. You can organize everything as you would with <code class="systemitem">BIND</code> not running in a <code class="command">chroot</code> environment.
+ </div><div class="para">
+ The following directories are automatically mounted into <code class="filename">/var/named/chroot/</code> if they are empty in the <code class="filename">/var/named/chroot/</code> directory. They must be kept empty if you want them to be mounted into <code class="filename">/var/named/chroot/</code>:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/etc/named</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/pki/dnssec-keys</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/run/named</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/var/named</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/lib64/bind</code> or <code class="filename">/usr/lib/bind</code> (architecture dependent).
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The following files are also mounted if the target file does not exist in <code class="filename">/var/named/chroot/</code>:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/etc/named.conf</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/rndc.conf</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/rndc.key</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/named.rfc1912.zones</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/named.dnssec.keys</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/named.iscdlv.key</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/named.root.key</code>
+ </div></li></ul></div>
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Editing files which have been mounted in a <code class="command">chroot</code> environment requires creating a backup copy and then editing the original file. Alternatively, use an editor with <span class="quote">“<span class="quote">edit-a-copy</span>”</span> mode disabled. For example, to edit the BIND's configuration file, <code class="filename">/etc/named.conf</code>, with Vim while it is running in a <code class="command">chroot</code> environment, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">vim -c "set backupcopy=yes" /etc/named.conf</code></pre>
+
+ </div></div></div><div class="section" id="sec-Installing_Bind_In_A_Chroot_Environment"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.2.1. Installing BIND in a chroot Environment</h4></div></div></div><div class="para">
+ To install <span class="application"><strong>BIND</strong></span> to run in a <code class="command">chroot</code> environment, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">yum install bind-chroot</code></pre>
+
+ </div><div class="para">
+ To enable the <code class="systemitem">named-chroot</code> service, first check if the <code class="systemitem">named</code> service is running by issuing the following command:
+<pre class="screen">~]$ <code class="command">systemctl status named</code></pre>
+ If it is running, it must be disabled.
+ </div><div class="para">
+ To disable <code class="systemitem">named</code>, issue the following commands as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl stop named</code></pre>
+
+<pre class="screen">~]# <code class="command">systemctl disable named</code></pre>
+ Then, to enable the <code class="systemitem">named-chroot</code> service, issue the following commands as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl enable named-chroot</code></pre>
+
+<pre class="screen">~]# <code class="command">systemctl start named-chroot</code></pre>
+
+ </div><div class="para">
+ To check the status of the <code class="systemitem">named-chroot</code> service, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl status named-chroot</code></pre>
+
+ </div></div><div class="section" id="sec-bind-namedconf-state"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.2.2. Common Statement Types</h4></div></div></div><div class="para">
+ The following types of statements are commonly used in <code class="filename">/etc/named.conf</code>:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225431147328" class="indexterm"></a>
+ <code class="option">acl</code> </span></dt><dd><div class="para">
+ The <code class="option">acl</code> (Access Control List) statement allows you to define groups of hosts, so that they can be permitted or denied access to the nameserver. It takes the following form:
+ </div><pre class="programlisting">acl <em class="replaceable"><code>acl-name</code></em> {
+ <em class="replaceable"><code>match-element</code></em>;
+ ...
+};</pre><div class="para">
+ The <em class="replaceable"><code>acl-name</code></em> statement name is the name of the access control list, and the <em class="replaceable"><code>match-element</code></em> option is usually an individual <code class="systemitem">IP</code> address (such as <code class="literal">10.0.1.1</code>) or a <em class="firstterm">Classless Inter-Domain Routing</em> (<acronym class="acronym">CIDR</acronym>) network notation (for example, <code class="literal">10.0.1.0/24</code>). For a list of already defined keywords, see <a class="xref" href="#table-bind-namedconf-common-acl">Table 10.2, “Predefined Access Control Lists”</a>.
+ </div><div class="table" id="table-bind-namedconf-common-acl"><h6>Table 10.2. Predefined Access Control Lists</h6><div class="table-contents"><table summary="Predefined Access Control Lists" border="1"><colgroup><col width="25%" class="keyword" /><col width="75%" class="description" /></colgroup><thead><tr><th class="">
+ Keyword
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="option">any</code>
+ </td><td class="">
+ Matches every <code class="systemitem">IP</code> address.
+ </td></tr><tr><td class="">
+ <code class="option">localhost</code>
+ </td><td class="">
+ Matches any <code class="systemitem">IP</code> address that is in use by the local system.
+ </td></tr><tr><td class="">
+ <code class="option">localnets</code>
+ </td><td class="">
+ Matches any <code class="systemitem">IP</code> address on any network to which the local system is connected.
+ </td></tr><tr><td class="">
+ <code class="option">none</code>
+ </td><td class="">
+ Does not match any <code class="systemitem">IP</code> address.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="option">acl</code> statement can be especially useful in conjunction with other statements such as <code class="option">options</code>. <a class="xref" href="#example-bind-namedconf-common-acl">Example 10.2, “Using acl in Conjunction with Options”</a> defines two access control lists, <code class="literal">black-hats</code> and <code class="literal">red-hats</code>, and adds <code class="literal">black-hats</code> on the blacklist while granting <code class="literal">red-hats</code> normal access.
+ </div><div class="example" id="example-bind-namedconf-common-acl"><h6>Example 10.2. Using acl in Conjunction with Options</h6><div class="example-contents"><pre class="programlisting">acl black-hats {
+ 10.0.2.0/24;
+ 192.168.0.0/24;
+ 1234:5678::9abc/24;
+};
+acl red-hats {
+ 10.0.1.0/24;
+};
+options {
+ blackhole { black-hats; };
+ allow-query { red-hats; };
+ allow-query-cache { red-hats; };
+};</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225449518944" class="indexterm"></a>
+ <code class="option">include</code> </span></dt><dd><div class="para">
+ The <code class="option">include</code> statement allows you to include files in the <code class="filename">/etc/named.conf</code>, so that potentially sensitive data can be placed in a separate file with restricted permissions. It takes the following form:
+ </div><pre class="programlisting">include "<em class="replaceable"><code>file-name</code></em>"</pre><div class="para">
+ The <em class="replaceable"><code>file-name</code></em> statement name is an absolute path to a file.
+ </div><div class="example" id="example-bind-namedconf-common-include"><h6>Example 10.3. Including a File to /etc/named.conf</h6><div class="example-contents"><pre class="programlisting">include "/etc/named.rfc1912.zones";</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225488608368" class="indexterm"></a>
+ <code class="option">options</code> </span></dt><dd><div class="para">
+ The <code class="option">options</code> statement allows you to define global server configuration options as well as to set defaults for other statements. It can be used to specify the location of the <code class="systemitem">named</code> working directory, the types of queries allowed, and much more. It takes the following form:
+ </div><pre class="programlisting">options {
+ <em class="replaceable"><code>option</code></em>;
+ ...
+};</pre><div class="para">
+ For a list of frequently used <em class="replaceable"><code>option</code></em> directives, see <a class="xref" href="#table-bind-namedconf-common-options">Table 10.3, “Commonly Used Configuration Options”</a> below.
+ </div><div class="table" id="table-bind-namedconf-common-options"><h6>Table 10.3. Commonly Used Configuration Options</h6><div class="table-contents"><table summary="Commonly Used Configuration Options" border="1"><colgroup><col width="25%" class="option" /><col width="75%" class="description" /></colgroup><thead><tr><th class="">
+ Option
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="option">allow-query</code>
+ </td><td class="">
+ Specifies which hosts are allowed to query the nameserver for authoritative resource records. It accepts an access control list, a collection of <code class="systemitem">IP</code> addresses, or networks in the CIDR notation. All hosts are allowed by default.
+ </td></tr><tr><td class="">
+ <code class="option">allow-query-cache</code>
+ </td><td class="">
+ Specifies which hosts are allowed to query the nameserver for non-authoritative data such as recursive queries. Only <code class="literal">localhost</code> and <code class="literal">localnets</code> are allowed by default.
+ </td></tr><tr><td class="">
+ <code class="option">blackhole</code>
+ </td><td class="">
+ Specifies which hosts are <span class="emphasis"><em>not</em></span> allowed to query the nameserver. This option should be used when a particular host or network floods the server with requests. The default option is <code class="literal">none</code>.
+ </td></tr><tr><td class="">
+ <code class="option">directory</code>
+ </td><td class="">
+ Specifies a working directory for the <code class="systemitem">named</code> service. The default option is <code class="literal">/var/named/</code>.
+ </td></tr><tr><td class="">
+ <code class="option">disable-empty-zone</code>
+ </td><td class="">
+ Used to disable one or more empty zones from the list of default prefixes that would be used. Can be specified in the options statement and also in view statements. It can be used multiple times.
+ </td></tr><tr><td class="">
+ <code class="option">dnssec-enable</code>
+ </td><td class="">
+ Specifies whether to return DNSSEC related resource records. The default option is <code class="literal">yes</code>.
+ </td></tr><tr><td class="">
+ <code class="option">dnssec-validation</code>
+ </td><td class="">
+ Specifies whether to prove that resource records are authentic via DNSSEC. The default option is <code class="literal">yes</code>.
+ </td></tr><tr><td class="">
+ <code class="option">empty-zones-enable</code>
+ </td><td class="">
+ Controls whether or not empty zones are created. Can be specified only in the options statement.
+ </td></tr><tr><td class="">
+ <code class="option">forwarders</code>
+ </td><td class="">
+ Specifies a list of valid <code class="systemitem">IP</code> addresses for nameservers to which the requests should be forwarded for resolution.
+ </td></tr><tr><td class="">
+ <code class="option">forward</code>
+ </td><td class="">
+ <div class="para">
+ Specifies the behavior of the <code class="option">forwarders</code> directive. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">first</code> — The server will query the nameservers listed in the <code class="option">forwarders</code> directive before attempting to resolve the name on its own.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">only</code> — When unable to query the nameservers listed in the <code class="option">forwarders</code> directive, the server will not attempt to resolve the name on its own.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="option">listen-on</code>
+ </td><td class="">
+ Specifies the <code class="systemitem">IPv4</code> network interface on which to listen for queries. On a <code class="systemitem">DNS</code> server that also acts as a gateway, you can use this option to answer queries originating from a single network only. All <code class="systemitem">IPv4</code> interfaces are used by default.
+ </td></tr><tr><td class="">
+ <code class="option">listen-on-v6</code>
+ </td><td class="">
+ Specifies the <code class="systemitem">IPv6</code> network interface on which to listen for queries. On a <code class="systemitem">DNS</code> server that also acts as a gateway, you can use this option to answer queries originating from a single network only. All <code class="systemitem">IPv6</code> interfaces are used by default.
+ </td></tr><tr><td class="">
+ <code class="option">max-cache-size</code>
+ </td><td class="">
+ Specifies the maximum amount of memory to be used for server caches. When the limit is reached, the server causes records to expire prematurely so that the limit is not exceeded. In a server with multiple views, the limit applies separately to the cache of each view. The default option is <code class="literal">32M</code>.
+ </td></tr><tr><td class="">
+ <code class="option">notify</code>
+ </td><td class="">
+ <div class="para">
+ Specifies whether to notify the secondary nameservers when a zone is updated. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — The server will notify all secondary nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — The server will <span class="emphasis"><em>not</em></span> notify any secondary nameserver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">master-only</code> — The server will notify primary server for the zone only.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">explicit</code> — The server will notify only the secondary servers that are specified in the <code class="option">also-notify</code> list within a zone statement.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="option">pid-file</code>
+ </td><td class="">
+ Specifies the location of the process ID file created by the <code class="systemitem">named</code> service.
+ </td></tr><tr><td class="">
+ <code class="option">recursion</code>
+ </td><td class="">
+ Specifies whether to act as a recursive server. The default option is <code class="literal">yes</code>.
+ </td></tr><tr><td class="">
+ <code class="option">statistics-file</code>
+ </td><td class="">
+ Specifies an alternate location for statistics files. The <code class="filename">/var/named/named.stats</code> file is used by default.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The directory used by <code class="systemitem">named</code> for runtime data has been moved from the BIND default location, <code class="filename">/var/run/named/</code>, to a new location <code class="filename">/run/named/</code>. As a result, the PID file has been moved from the default location <code class="filename">/var/run/named/named.pid</code> to the new location <code class="filename">/run/named/named.pid</code>. In addition, the session-key file has been moved to <code class="filename">/run/named/session.key</code>. These locations need to be specified by statements in the options section. See <a class="xref" href="#example-bind-namedconf-common-options">Example 10.4, “Using the options Statement”</a>.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Restrict recursive servers to selected clients only</h2></div><div class="admonition"><div class="para">
+ To prevent distributed denial of service (DDoS) attacks, it is recommended that you use the <code class="option">allow-query-cache</code> option to restrict recursive <code class="systemitem">DNS</code> services for a particular subset of clients only.
+ </div></div></div><div class="para">
+ Refer to the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="#sec-bind-installed-docs">Section 10.2.8.1, “Installed Documentation”</a>, and the <code class="filename">named.conf</code> manual page for a complete list of available options.
+ </div><div class="example" id="example-bind-namedconf-common-options"><h6>Example 10.4. Using the options Statement</h6><div class="example-contents"><pre class="programlisting">options {
+ allow-query { localhost; };
+ listen-on port 53 { 127.0.0.1; };
+ listen-on-v6 port 53 { ::1; };
+ max-cache-size 256M;
+ directory "/var/named";
+ statistics-file "/var/named/data/named_stats.txt";
+
+ recursion yes;
+ dnssec-enable yes;
+ dnssec-validation yes;
+
+ pid-file "/run/named/named.pid";
+ session-keyfile "/run/named/session.key";
+};</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225407326416" class="indexterm"></a>
+ <code class="option">zone</code> </span></dt><dd><div class="para">
+ The <code class="option">zone</code> statement allows you to define the characteristics of a zone, such as the location of its configuration file and zone-specific options, and can be used to override the global <code class="option">options</code> statements. It takes the following form:
+ </div><pre class="programlisting">zone <em class="replaceable"><code>zone-name</code></em> [<em class="replaceable"><code>zone-class</code></em>] {
+ <em class="replaceable"><code>option</code></em>;
+ ...
+};</pre><div class="para">
+ The <em class="replaceable"><code>zone-name</code></em> attribute is the name of the zone, <em class="replaceable"><code>zone-class</code></em> is the optional class of the zone, and <em class="replaceable"><code>option</code></em> is a <code class="option">zone</code> statement option as described in <a class="xref" href="#table-bind-namedconf-common-zone">Table 10.4, “Commonly Used Options in Zone Statements”</a>.
+ </div><div class="para">
+ The <em class="replaceable"><code>zone-name</code></em> attribute is particularly important, as it is the default value assigned for the <code class="option">$ORIGIN</code> directive used within the corresponding zone file located in the <code class="filename">/var/named/</code> directory. The <code class="systemitem">named</code> daemon appends the name of the zone to any non-fully qualified domain name listed in the zone file. For example, if a <code class="option">zone</code> statement defines the namespace for <code class="literal">example.com</code>, use <code class="literal">example.com</code> as the <em class="replaceable"><code>zone-name</code></em> so that it is placed at the end of host names within the <code class="literal">example.com</code> zone file.
+ </div><div class="para">
+ For more information about zone files, refer to <a class="xref" href="#sec-bind-zone">Section 10.2.3, “Editing Zone Files”</a>.
+ </div><div class="table" id="table-bind-namedconf-common-zone"><h6>Table 10.4. Commonly Used Options in Zone Statements</h6><div class="table-contents"><table summary="Commonly Used Options in Zone Statements" border="1"><colgroup><col width="25%" class="option" /><col width="75%" class="description" /></colgroup><thead><tr><th class="">
+ Option
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="option">allow-query</code>
+ </td><td class="">
+ Specifies which clients are allowed to request information about this zone. This option overrides global <code class="option">allow-query</code> option. All query requests are allowed by default.
+ </td></tr><tr><td class="">
+ <code class="option">allow-transfer</code>
+ </td><td class="">
+ Specifies which secondary servers are allowed to request a transfer of the zone's information. All transfer requests are allowed by default.
+ </td></tr><tr><td class="">
+ <code class="option">allow-update</code>
+ </td><td class="">
+ <div class="para">
+ Specifies which hosts are allowed to dynamically update information in their zone. The default option is to deny all dynamic update requests.
+ </div>
+ <div class="para">
+ Note that you should be careful when allowing hosts to update information about their zone. Do not set <code class="systemitem">IP</code> addresses in this option unless the server is in the trusted network. Instead, use TSIG key as described in <a class="xref" href="#sec-bind-features-tsig">Section 10.2.6.3, “Transaction SIGnatures (TSIG)”</a>.
+ </div>
+
+ </td></tr><tr><td class="">
+ <code class="option">file</code>
+ </td><td class="">
+ Specifies the name of the file in the <code class="systemitem">named</code> working directory that contains the zone's configuration data.
+ </td></tr><tr><td class="">
+ <code class="option">masters</code>
+ </td><td class="">
+ Specifies from which <code class="systemitem">IP</code> addresses to request authoritative zone information. This option is used only if the zone is defined as <code class="option">type</code> <code class="option">slave</code>.
+ </td></tr><tr><td class="">
+ <code class="option">notify</code>
+ </td><td class="">
+ <div class="para">
+ Specifies whether to notify the secondary nameservers when a zone is updated. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">yes</code> — The server will notify all secondary nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">no</code> — The server will <span class="emphasis"><em>not</em></span> notify any secondary nameserver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master-only</code> — The server will notify primary server for the zone only.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">explicit</code> — The server will notify only the secondary servers that are specified in the <code class="option">also-notify</code> list within a zone statement.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="option">type</code>
+ </td><td class="">
+ <div class="para">
+ Specifies the zone type. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">delegation-only</code> — Enforces the delegation status of infrastructure zones such as COM, NET, or ORG. Any answer that is received without an explicit or implicit delegation is treated as <code class="literal">NXDOMAIN</code>. This option is only applicable in TLDs (Top-Level Domain) or root zone files used in recursive or caching implementations.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">forward</code> — Forwards all requests for information about this zone to other nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">hint</code> — A special type of zone used to point to the root nameservers which resolve queries when a zone is not otherwise known. No configuration beyond the default is necessary with a <code class="option">hint</code> zone.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master</code> — Designates the nameserver as authoritative for this zone. A zone should be set as the <code class="option">master</code> if the zone's configuration files reside on the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">slave</code> — Designates the nameserver as a slave server for this zone. Master server is specified in <code class="option">masters</code> directive.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Most changes to the <code class="filename">/etc/named.conf</code> file of a primary or secondary nameserver involve adding, modifying, or deleting <code class="option">zone</code> statements, and only a small subset of <code class="option">zone</code> statement options is usually needed for a nameserver to work efficiently.
+ </div><div class="para">
+ In <a class="xref" href="#example-bind-namedconf-common-zone-primary">Example 10.5, “A Zone Statement for a Primary nameserver”</a>, the zone is identified as <code class="literal">example.com</code>, the type is set to <code class="literal">master</code>, and the <code class="systemitem">named</code> service is instructed to read the <code class="filename">/var/named/example.com.zone</code> file. It also allows only a secondary nameserver (<code class="literal">192.168.0.2</code>) to transfer the zone.
+ </div><div class="example" id="example-bind-namedconf-common-zone-primary"><h6>Example 10.5. A Zone Statement for a Primary nameserver</h6><div class="example-contents"><pre class="programlisting">zone "example.com" IN {
+ type master;
+ file "example.com.zone";
+ allow-transfer { 192.168.0.2; };
+};</pre></div></div><br class="example-break" /><div class="para">
+ A secondary server's <code class="option">zone</code> statement is slightly different. The type is set to <code class="literal">slave</code>, and the <code class="literal">masters</code> directive is telling <code class="systemitem">named</code> the <code class="systemitem">IP</code> address of the master server.
+ </div><div class="para">
+ In <a class="xref" href="#example-bind-namedconf-common-zone-secondary">Example 10.6, “A Zone Statement for a Secondary nameserver”</a>, the <code class="systemitem">named</code> service is configured to query the primary server at the <code class="literal">192.168.0.1</code> <code class="systemitem">IP</code> address for information about the <code class="literal">example.com</code> zone. The received information is then saved to the <code class="filename">/var/named/slaves/example.com.zone</code> file. Note that you have to put all slave zones in the <code class="filename">/var/named/slaves/</code> directory, otherwise the service will fail to transfer the zone.
+ </div><div class="example" id="example-bind-namedconf-common-zone-secondary"><h6>Example 10.6. A Zone Statement for a Secondary nameserver</h6><div class="example-contents"><pre class="programlisting">zone "example.com" {
+ type slave;
+ file "slaves/example.com.zone";
+ masters { 192.168.0.1; };
+};</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="sec-bind-namedconf-state-other"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.2.3. Other Statement Types</h4></div></div></div><div class="para">
+ The following types of statements are less commonly used in <code class="filename">/etc/named.conf</code>:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225486254144" class="indexterm"></a>
+ <code class="option">controls</code> </span></dt><dd><div class="para">
+ The <code class="option">controls</code> statement allows you to configure various security requirements necessary to use the <code class="command">rndc</code> command to administer the <code class="systemitem">named</code> service.
+ </div><div class="para">
+ Refer to <a class="xref" href="#sec-bind-rndc">Section 10.2.4, “Using the rndc Utility”</a> for more information on the <code class="command">rndc</code> utility and its usage.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225459873824" class="indexterm"></a>
+ <code class="option">key</code> </span></dt><dd><div class="para">
+ The <code class="option">key</code> statement allows you to define a particular key by name. Keys are used to authenticate various actions, such as secure updates or the use of the <code class="command">rndc</code> command. Two options are used with <code class="option">key</code>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">algorithm <em class="replaceable"><code>algorithm-name</code></em></code> — The type of algorithm to be used (for example, <code class="literal">hmac-md5</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">secret "<em class="replaceable"><code>key-value</code></em>"</code> — The encrypted key.
+ </div></li></ul></div><div class="para">
+ Refer to <a class="xref" href="#sec-bind-rndc">Section 10.2.4, “Using the rndc Utility”</a> for more information on the <code class="command">rndc</code> utility and its usage.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225461160944" class="indexterm"></a>
+ <code class="option">logging</code> </span></dt><dd><div class="para">
+ The <code class="option">logging</code> statement allows you to use multiple types of logs, so called <em class="firstterm">channels</em>. By using the <code class="option">channel</code> option within the statement, you can construct a customized type of log with its own file name (<code class="option">file</code>), size limit (<code class="option">size</code>), version number (<code class="option">version</code>), and level of importance (<code class="option">severity</code>). Once a customized channel is defined, a <code class="option">category</code> option is used to categorize the channel and begin logging when the <code class="systemitem">named</code> service is restarted.
+ </div><div class="para">
+ By default, <code class="systemitem">named</code> sends standard messages to the <code class="systemitem">rsyslog</code> daemon, which places them in <code class="filename">/var/log/messages</code>. Several standard channels are built into BIND with various severity levels, such as <code class="literal">default_syslog</code> (which handles informational logging messages) and <code class="literal">default_debug</code> (which specifically handles debugging messages). A default category, called <code class="literal">default</code>, uses the built-in channels to do normal logging without any special configuration.
+ </div><div class="para">
+ Customizing the logging process can be a very detailed process and is beyond the scope of this chapter. For information on creating custom BIND logs, refer to the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="#sec-bind-installed-docs">Section 10.2.8.1, “Installed Documentation”</a>.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225443285088" class="indexterm"></a>
+ <code class="option">server</code> </span></dt><dd><div class="para">
+ The <code class="option">server</code> statement allows you to specify options that affect how the <code class="systemitem">named</code> service should respond to remote nameservers, especially with regard to notifications and zone transfers.
+ </div><div class="para">
+ The <code class="option">transfer-format</code> option controls the number of resource records that are sent with each message. It can be either <code class="literal">one-answer</code> (only one resource record), or <code class="literal">many-answers</code> (multiple resource records). Note that while the <code class="literal">many-answers</code> option is more efficient, it is not supported by older versions of BIND.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225428527072" class="indexterm"></a>
+ <code class="option">trusted-keys</code> </span></dt><dd><div class="para">
+ The <code class="option">trusted-keys</code> statement allows you to specify assorted public keys used for secure <code class="systemitem">DNS</code> (DNSSEC). Refer to <a class="xref" href="#sec-bind-features-dnssec">Section 10.2.6.4, “DNS Security Extensions (DNSSEC)”</a> for more information on this topic.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225439662544" class="indexterm"></a>
+ <code class="option">view</code> </span></dt><dd><div class="para">
+ The <code class="option">view</code> statement allows you to create special views depending upon which network the host querying the nameserver is on. This allows some hosts to receive one answer regarding a zone while other hosts receive totally different information. Alternatively, certain zones may only be made available to particular trusted hosts while non-trusted hosts can only make queries for other zones.
+ </div><div class="para">
+ Multiple views can be used as long as their names are unique. The <code class="option">match-clients</code> option allows you to specify the <code class="systemitem">IP</code> addresses that apply to a particular view. If the <code class="option">options</code> statement is used within a view, it overrides the already configured global options. Finally, most <code class="option">view</code> statements contain multiple <code class="option">zone</code> statements that apply to the <code class="option">match-clients</code> list.
+ </div><div class="para">
+ Note that the order in which the <code class="option">view</code> statements are listed is important, as the first statement that matches a particular client's <code class="systemitem">IP</code> address is used. For more information on this topic, refer to <a class="xref" href="#sec-bind-features-views">Section 10.2.6.1, “Multiple Views”</a>.
+ </div></dd></dl></div></div><div class="section" id="sec-bind-namedconf-comm"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.2.4. Comment Tags</h4></div></div></div><a id="idm225479763664" class="indexterm"></a><div class="para">
+ Additionally to statements, the <code class="filename">/etc/named.conf</code> file can also contain comments. Comments are ignored by the <code class="systemitem">named</code> service, but can prove useful when providing additional information to a user. The following are valid comment tags:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="literal">//</code> </span></dt><dd><div class="para">
+ Any text after the <code class="literal">//</code> characters to the end of the line is considered a comment. For example:
+ </div><pre class="programlisting">notify yes; // notify all secondary nameservers</pre></dd><dt class="varlistentry"><span class="term"> <code class="literal">#</code> </span></dt><dd><div class="para">
+ Any text after the <code class="literal">#</code> character to the end of the line is considered a comment. For example:
+ </div><pre class="programlisting">notify yes; # notify all secondary nameservers</pre></dd><dt class="varlistentry"><span class="term"><code class="literal">/*</code> and <code class="literal">*/</code></span></dt><dd><div class="para">
+ Any block of text enclosed in <code class="literal">/*</code> and <code class="literal">*/</code> is considered a comment. For example:
+ </div><pre class="programlisting">notify yes; /* notify all secondary nameservers */</pre></dd></dl></div></div></div><div class="section" id="sec-bind-zone"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.3. Editing Zone Files</h3></div></div></div><a id="idm225456361232" class="indexterm"></a><a id="idm225455861184" class="indexterm"></a><a id="idm225455863264" class="indexterm"></a><a id="idm225456361712" class="indexterm"></a><div class="para">
+ As outlined in <a class="xref" href="#sec-dns-introduction-zones">Section 10.1.1, “Nameserver Zones”</a>, zone files contain information about a namespace. They are stored in the <code class="systemitem">named</code> working directory located in <code class="filename">/var/named/</code> by default. Each zone file is named according to the <code class="option">file</code> option in the <code class="option">zone</code> statement, usually in a way that relates to the domain in and identifies the file as containing zone data, such as <code class="filename">example.com.zone</code>.
+ </div><div class="table" id="table-bind-zone-files"><h6>Table 10.5. The named Service Zone Files</h6><div class="table-contents"><table summary="The named Service Zone Files" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Path
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="filename">/var/named/</code>
+ </td><td class="">
+ The working directory for the <code class="systemitem">named</code> service. The nameserver is <span class="emphasis"><em>not</em></span> allowed to write to this directory.
+ </td></tr><tr><td class="">
+ <code class="filename">/var/named/slaves/</code>
+ </td><td class="">
+ The directory for secondary zones. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr><tr><td class="">
+ <code class="filename">/var/named/dynamic/</code>
+ </td><td class="">
+ The directory for other files, such as dynamic <code class="systemitem">DNS</code> (DDNS) zones or managed DNSSEC keys. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr><tr><td class="">
+ <code class="filename">/var/named/data/</code>
+ </td><td class="">
+ The directory for various statistics and debugging files. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ A zone file consists of directives and resource records. Directives tell the nameserver to perform tasks or apply special settings to the zone, resource records define the parameters of the zone and assign identities to individual hosts. While the directives are optional, the resource records are required in order to provide name service to a zone.
+ </div><div class="para">
+ All directives and resource records should be entered on individual lines.
+ </div><div class="section" id="sec-bind-zone-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.3.1. Common Directives</h4></div></div></div><div class="para">
+ Directives begin with the dollar sign character (<code class="literal">$</code>) followed by the name of the directive, and usually appear at the top of the file. The following directives are commonly used in zone files:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225427497264" class="indexterm"></a>
+ <code class="command">$INCLUDE</code> </span></dt><dd><div class="para">
+ The <code class="command">$INCLUDE</code> directive allows you to include another file at the place where it appears, so that other zone settings can be stored in a separate zone file.
+ </div><div class="example" id="example-bind-zone-directive-include"><h6>Example 10.7. Using the $INCLUDE Directive</h6><div class="example-contents"><pre class="programlisting">$INCLUDE /var/named/penguin.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225459628304" class="indexterm"></a>
+ <code class="command">$ORIGIN</code> </span></dt><dd><div class="para">
+ The <code class="command">$ORIGIN</code> directive allows you to append the domain name to unqualified records, such as those with the host name only. Note that the use of this directive is not necessary if the zone is specified in <code class="filename">/etc/named.conf</code>, since the zone name is used by default.
+ </div><div class="para">
+ In <a class="xref" href="#example-bind-zone-directive-origin">Example 10.8, “Using the $ORIGIN Directive”</a>, any names used in resource records that do not end in a trailing period (the <code class="literal">.</code> character) are appended with <code class="literal">example.com</code>.
+ </div><div class="example" id="example-bind-zone-directive-origin"><h6>Example 10.8. Using the $ORIGIN Directive</h6><div class="example-contents"><pre class="programlisting">$ORIGIN example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225458779920" class="indexterm"></a>
+ <code class="command">$TTL</code> </span></dt><dd><div class="para">
+ The <code class="command">$TTL</code> directive allows you to set the default <em class="firstterm">Time to Live</em> (TTL) value for the zone, that is, how long is a zone record valid. Each resource record can contain its own TTL value, which overrides this directive.
+ </div><div class="para">
+ Increasing this value allows remote nameservers to cache the zone information for a longer period of time, reducing the number of queries for the zone and lengthening the amount of time required to propagate resource record changes.
+ </div><div class="example" id="example-bind-zone-directive-ttl"><h6>Example 10.9. Using the $TTL Directive</h6><div class="example-contents"><pre class="programlisting">$TTL 1D</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="sec-bind-zone-rr"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.3.2. Common Resource Records</h4></div></div></div><div class="para">
+ The following resource records are commonly used in zone files:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225412498096" class="indexterm"></a>
+ <code class="command">A</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Address</em> record specifies an <code class="systemitem">IP</code> address to be assigned to a name. It takes the following form:
+ </div><pre class="programlisting"><em class="replaceable"><code>hostname</code></em> IN A <em class="replaceable"><code>IP-address</code></em></pre><div class="para">
+ If the <em class="replaceable"><code>hostname</code></em> value is omitted, the record will point to the last specified <em class="replaceable"><code>hostname</code></em>.
+ </div><div class="para">
+ In <a class="xref" href="#example-bind-zone-rr-a">Example 10.10, “Using the A Resource Record”</a>, the requests for <code class="systemitem">server1.example.com</code> are pointed to <code class="literal">10.0.1.3</code> or <code class="literal">10.0.1.5</code>.
+ </div><div class="example" id="example-bind-zone-rr-a"><h6>Example 10.10. Using the A Resource Record</h6><div class="example-contents"><pre class="programlisting">server1 IN A 10.0.1.3
+ IN A 10.0.1.5</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225463189024" class="indexterm"></a>
+ <code class="command">CNAME</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Canonical Name</em> record maps one name to another. Because of this, this type of record is sometimes referred to as an <em class="firstterm">alias record</em>. It takes the following form:
+ </div><pre class="programlisting"><em class="replaceable"><code>alias-name</code></em> IN CNAME <em class="replaceable"><code>real-name</code></em></pre><div class="para">
+ <code class="command">CNAME</code> records are most commonly used to point to services that use a common naming scheme, such as <code class="literal">www</code> for Web servers. However, there are multiple restrictions for their usage:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ CNAME records should not point to other CNAME records. This is mainly to avoid possible infinite loops.
+ </div></li><li class="listitem"><div class="para">
+ CNAME records should not contain other resource record types (such as A, NS, MX, etc.). The only exception are DNSSEC related records (RRSIG, NSEC, etc.) when the zone is signed.
+ </div></li><li class="listitem"><div class="para">
+ Other resource records that point to the fully qualified domain name (FQDN) of a host (NS, MX, PTR) should not point to a CNAME record.
+ </div></li></ul></div><div class="para">
+ In <a class="xref" href="#example-bind-zone-rr-cname">Example 10.11, “Using the CNAME Resource Record”</a>, the <code class="command">A</code> record binds a host name to an <code class="systemitem">IP</code> address, while the <code class="command">CNAME</code> record points the commonly used <code class="literal">www</code> host name to it.
+ </div><div class="example" id="example-bind-zone-rr-cname"><h6>Example 10.11. Using the CNAME Resource Record</h6><div class="example-contents"><pre class="programlisting">server1 IN A 10.0.1.5
+www IN CNAME server1</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225444875600" class="indexterm"></a>
+ <code class="command">MX</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Mail Exchange</em> record specifies where the mail sent to a particular namespace controlled by this zone should go. It takes the following form:
+ </div><pre class="programlisting">IN MX <em class="replaceable"><code>preference-value</code></em> <em class="replaceable"><code>email-server-name</code></em></pre><div class="para">
+ The <em class="replaceable"><code>email-server-name</code></em> is a fully qualified domain name (FQDN). The <em class="replaceable"><code>preference-value</code></em> allows numerical ranking of the email servers for a namespace, giving preference to some email systems over others. The <code class="command">MX</code> resource record with the lowest <em class="replaceable"><code>preference-value</code></em> is preferred over the others. However, multiple email servers can possess the same value to distribute email traffic evenly among them.
+ </div><div class="para">
+ In <a class="xref" href="#example-bind-zone-rr-mx">Example 10.12, “Using the MX Resource Record”</a>, the first <code class="systemitem">mail.example.com</code> email server is preferred to the <code class="systemitem">mail2.example.com</code> email server when receiving email destined for the <code class="systemitem">example.com</code> domain.
+ </div><div class="example" id="example-bind-zone-rr-mx"><h6>Example 10.12. Using the MX Resource Record</h6><div class="example-contents"><pre class="programlisting">example.com. IN MX 10 mail.example.com.
+ IN MX 20 mail2.example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225447594752" class="indexterm"></a>
+ <code class="command">NS</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Nameserver</em> record announces authoritative nameservers for a particular zone. It takes the following form:
+ </div><pre class="programlisting">IN NS <em class="replaceable"><code>nameserver-name</code></em></pre><div class="para">
+ The <em class="replaceable"><code>nameserver-name</code></em> should be a fully qualified domain name (FQDN). Note that when two nameservers are listed as authoritative for the domain, it is not important whether these nameservers are secondary nameservers, or if one of them is a primary server. They are both still considered authoritative.
+ </div><div class="example" id="example-bind-zone-rr-ns"><h6>Example 10.13. Using the NS Resource Record</h6><div class="example-contents"><pre class="programlisting">IN NS dns1.example.com.
+IN NS dns2.example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225426121200" class="indexterm"></a>
+ <code class="command">PTR</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Pointer</em> record points to another part of the namespace. It takes the following form:
+ </div><pre class="programlisting"><em class="replaceable"><code>last-IP-digit</code></em> IN PTR <em class="replaceable"><code>FQDN-of-system</code></em></pre><div class="para">
+ The <em class="replaceable"><code>last-IP-digit</code></em> directive is the last number in an <code class="systemitem">IP</code> address, and the <em class="replaceable"><code>FQDN-of-system</code></em> is a fully qualified domain name (FQDN).
+ </div><div class="para">
+ <code class="command">PTR</code> records are primarily used for reverse name resolution, as they point <code class="systemitem">IP</code> addresses back to a particular name. Refer to <a class="xref" href="#sec-bind-configuration-zone-reverse">Section 10.2.3.4.2, “A Reverse Name Resolution Zone File”</a> for examples of <code class="command">PTR</code> records in use.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225447036560" class="indexterm"></a>
+ <code class="command">SOA</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Start of Authority</em> record announces important authoritative information about a namespace to the nameserver. Located after the directives, it is the first resource record in a zone file. It takes the following form:
+ </div><pre class="programlisting">@ IN SOA <em class="replaceable"><code>primary-name-server</code></em> <em class="replaceable"><code>hostmaster-email</code></em> (
+ <em class="replaceable"><code>serial-number</code></em>
+ <em class="replaceable"><code>time-to-refresh</code></em>
+ <em class="replaceable"><code>time-to-retry</code></em>
+ <em class="replaceable"><code>time-to-expire</code></em>
+ <em class="replaceable"><code>minimum-TTL</code></em> )</pre><div class="para">
+ The directives are as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="literal">@</code> symbol places the <code class="command">$ORIGIN</code> directive (or the zone's name if the <code class="command">$ORIGIN</code> directive is not set) as the namespace being defined by this <code class="command">SOA</code> resource record.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>primary-name-server</code></em> directive is the host name of the primary nameserver that is authoritative for this domain.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>hostmaster-email</code></em> directive is the email of the person to contact about the namespace.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>serial-number</code></em> directive is a numerical value incremented every time the zone file is altered to indicate it is time for the <code class="systemitem">named</code> service to reload the zone.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>time-to-refresh</code></em> directive is the numerical value secondary nameservers use to determine how long to wait before asking the primary nameserver if any changes have been made to the zone.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>time-to-retry</code></em> directive is a numerical value used by secondary nameservers to determine the length of time to wait before issuing a refresh request in the event that the primary nameserver is not answering. If the primary server has not replied to a refresh request before the amount of time specified in the <em class="replaceable"><code>time-to-expire</code></em> directive elapses, the secondary servers stop responding as an authority for requests concerning that namespace.
+ </div></li><li class="listitem"><div class="para">
+ In BIND 4 and 8, the <em class="replaceable"><code>minimum-TTL</code></em> directive is the amount of time other nameservers cache the zone's information. In BIND 9, it defines how long negative answers are cached for. Caching of negative answers can be set to a maximum of 3 hours (<code class="option">3H</code>).
+ </div></li></ul></div><div class="para">
+ When configuring BIND, all times are specified in seconds. However, it is possible to use abbreviations when specifying units of time other than seconds, such as minutes (<code class="literal">M</code>), hours (<code class="literal">H</code>), days (<code class="literal">D</code>), and weeks (<code class="literal">W</code>). <a class="xref" href="#tb-bind-seconds">Table 10.6, “Seconds compared to other time units”</a> shows an amount of time in seconds and the equivalent time in another format.
+ </div><div class="table" id="tb-bind-seconds"><h6>Table 10.6. Seconds compared to other time units</h6><div class="table-contents"><table summary="Seconds compared to other time units" border="1"><colgroup><col width="50%" class="seconds" /><col width="50%" class="other" /></colgroup><thead><tr><th class="">
+ Seconds
+ </th><th class="">
+ Other Time Units
+ </th></tr></thead><tbody><tr><td class="">
+ 60
+ </td><td class="">
+ <code class="literal">1M</code>
+ </td></tr><tr><td class="">
+ 1800
+ </td><td class="">
+ <code class="literal">30M</code>
+ </td></tr><tr><td class="">
+ 3600
+ </td><td class="">
+ <code class="literal">1H</code>
+ </td></tr><tr><td class="">
+ 10800
+ </td><td class="">
+ <code class="literal">3H</code>
+ </td></tr><tr><td class="">
+ 21600
+ </td><td class="">
+ <code class="literal">6H</code>
+ </td></tr><tr><td class="">
+ 43200
+ </td><td class="">
+ <code class="literal">12H</code>
+ </td></tr><tr><td class="">
+ 86400
+ </td><td class="">
+ <code class="literal">1D</code>
+ </td></tr><tr><td class="">
+ 259200
+ </td><td class="">
+ <code class="literal">3D</code>
+ </td></tr><tr><td class="">
+ 604800
+ </td><td class="">
+ <code class="literal">1W</code>
+ </td></tr><tr><td class="">
+ 31536000
+ </td><td class="">
+ <code class="literal">365D</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-bind-zone-rr-soa"><h6>Example 10.14. Using the SOA Resource Record</h6><div class="example-contents"><pre class="programlisting">@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="sec-bind-zone-comm"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.3.3. Comment Tags</h4></div></div></div><a id="idm225408518608" class="indexterm"></a><div class="para">
+ Additionally to resource records and directives, a zone file can also contain comments. Comments are ignored by the <code class="systemitem">named</code> service, but can prove useful when providing additional information to the user. Any text after the semicolon character (<code class="literal">;</code>) to the end of the line is considered a comment. For example:
+ </div><pre class="programlisting"> 604800 ; expire after 1 week</pre></div><div class="section" id="sec-bind-zone-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.3.4. Example Usage</h4></div></div></div><div class="para">
+ The following examples show the basic usage of zone files.
+ </div><div class="section" id="sec-bind-zone-examples-basic"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">10.2.3.4.1. A Simple Zone File</h5></div></div></div><a id="idm225448085504" class="indexterm"></a><div class="para">
+ <a class="xref" href="#example-bind-zone-examples-basic">Example 10.15, “A simple zone file”</a> demonstrates the use of standard directives and <code class="command">SOA</code> values.
+ </div><div class="example" id="example-bind-zone-examples-basic"><h6>Example 10.15. A simple zone file</h6><div class="example-contents"><pre class="programlisting">$ORIGIN example.com.
+$TTL 86400
+@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day
+;
+;
+ IN NS dns1.example.com.
+ IN NS dns2.example.com.
+dns1 IN A 10.0.1.1
+ IN AAAA aaaa:bbbb::1
+dns2 IN A 10.0.1.2
+ IN AAAA aaaa:bbbb::2
+;
+;
+@ IN MX 10 mail.example.com.
+ IN MX 20 mail2.example.com.
+mail IN A 10.0.1.5
+ IN AAAA aaaa:bbbb::5
+mail2 IN A 10.0.1.6
+ IN AAAA aaaa:bbbb::6
+;
+;
+; This sample zone file illustrates sharing the same IP addresses
+; for multiple services:
+;
+services IN A 10.0.1.10
+ IN AAAA aaaa:bbbb::10
+ IN A 10.0.1.11
+ IN AAAA aaaa:bbbb::11
+
+ftp IN CNAME services.example.com.
+www IN CNAME services.example.com.
+;
+;</pre></div></div><br class="example-break" /><div class="para">
+ In this example, the authoritative nameservers are set as <code class="systemitem">dns1.example.com</code> and <code class="systemitem">dns2.example.com</code>, and are tied to the <code class="systemitem">10.0.1.1</code> and <code class="systemitem">10.0.1.2</code> <code class="systemitem">IP</code> addresses respectively using the <code class="command">A</code> record.
+ </div><div class="para">
+ The email servers configured with the <code class="command">MX</code> records point to <code class="systemitem">mail</code> and <code class="systemitem">mail2</code> via <code class="command">A</code> records. Since these names do not end in a trailing period (<code class="literal">.</code> character), the <code class="command">$ORIGIN</code> domain is placed after them, expanding them to <code class="systemitem">mail.example.com</code> and <code class="systemitem">mail2.example.com</code>.
+ </div><div class="para">
+ Services available at the standard names, such as <code class="systemitem">www.example.com</code> (<acronym class="acronym">WWW</acronym>), are pointed at the appropriate servers using the <code class="command">CNAME</code> record.
+ </div><div class="para">
+ This zone file would be called into service with a <code class="command">zone</code> statement in the <code class="filename">/etc/named.conf</code> similar to the following:
+ </div><pre class="programlisting">zone "example.com" IN {
+ type master;
+ file "example.com.zone";
+ allow-update { none; };
+};</pre></div><div class="section" id="sec-bind-configuration-zone-reverse"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">10.2.3.4.2. A Reverse Name Resolution Zone File</h5></div></div></div><a id="idm225459868800" class="indexterm"></a><div class="para">
+ A reverse name resolution zone file is used to translate an <code class="systemitem">IP</code> address in a particular namespace into a fully qualified domain name (FQDN). It looks very similar to a standard zone file, except that the <code class="command">PTR</code> resource records are used to link the <code class="systemitem">IP</code> addresses to a fully qualified domain name as shown in <a class="xref" href="#example-bind-zone-examples-reverse">Example 10.16, “A reverse name resolution zone file”</a>.
+ </div><div class="example" id="example-bind-zone-examples-reverse"><h6>Example 10.16. A reverse name resolution zone file</h6><div class="example-contents"><pre class="programlisting">$ORIGIN 1.0.10.in-addr.arpa.
+$TTL 86400
+@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day
+;
+@ IN NS dns1.example.com.
+;
+1 IN PTR dns1.example.com.
+2 IN PTR dns2.example.com.
+;
+5 IN PTR server1.example.com.
+6 IN PTR server2.example.com.
+;
+3 IN PTR ftp.example.com.
+4 IN PTR ftp.example.com.</pre></div></div><br class="example-break" /><div class="para">
+ In this example, <code class="systemitem">IP</code> addresses <code class="systemitem">10.0.1.1</code> through <code class="systemitem">10.0.1.6</code> are pointed to the corresponding fully qualified domain name.
+ </div><div class="para">
+ This zone file would be called into service with a <code class="option">zone</code> statement in the <code class="filename">/etc/named.conf</code> file similar to the following:
+ </div><pre class="programlisting">zone "1.0.10.in-addr.arpa" IN {
+ type master;
+ file "example.com.rr.zone";
+ allow-update { none; };
+};</pre><div class="para">
+ There is very little difference between this example and a standard <code class="command">zone</code> statement, except for the zone name. Note that a reverse name resolution zone requires the first three blocks of the <code class="systemitem">IP</code> address reversed followed by <code class="command">.in-addr.arpa</code>. This allows the single block of <code class="systemitem">IP</code> numbers used in the reverse name resolution zone file to be associated with the zone.
+ </div></div></div></div><div class="section" id="sec-bind-rndc"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.4. Using the rndc Utility</h3></div></div></div><a id="idm225464357904" class="indexterm"></a><div class="para">
+ The <code class="command">rndc</code> utility is a command-line tool that allows you to administer the <code class="systemitem">named</code> service, both locally and from a remote machine. Its usage is as follows:
+ </div><pre class="screen"><code class="command">rndc</code> [<em class="replaceable"><code>option</code></em>...] <em class="replaceable"><code>command</code></em> [<em class="replaceable"><code>command-option</code></em>]</pre><div class="section" id="sec-bind-rndc-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.4.1. Configuring the Utility</h4></div></div></div><div class="para">
+ To prevent unauthorized access to the service, <code class="systemitem">named</code> must be configured to listen on the selected port (<code class="literal">953</code> by default), and an identical key must be used by both the service and the <code class="command">rndc</code> utility.
+ </div><div class="table" id="table-bind-rndc-configuration-files"><h6>Table 10.7. Relevant files</h6><div class="table-contents"><table summary="Relevant files" border="1"><colgroup><col width="38%" class="path" /><col width="63%" class="description" /></colgroup><thead><tr><th class="">
+ Path
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <a id="idm225483764496" class="indexterm"></a>
+ <code class="filename">/etc/named.conf</code>
+ </td><td class="">
+ The default configuration file for the <code class="systemitem">named</code> service.
+ </td></tr><tr><td class="">
+ <a id="idm225440389824" class="indexterm"></a>
+ <code class="filename">/etc/rndc.conf</code>
+ </td><td class="">
+ The default configuration file for the <code class="command">rndc</code> utility.
+ </td></tr><tr><td class="">
+ <a id="idm225456644640" class="indexterm"></a>
+ <code class="filename">/etc/rndc.key</code>
+ </td><td class="">
+ The default key location.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="command">rndc</code> configuration is located in <code class="filename">/etc/rndc.conf</code>. If the file does not exist, the utility will use the key located in <code class="filename">/etc/rndc.key</code>, which was generated automatically during the installation process using the <code class="command">rndc-confgen -a</code> command.
+ </div><div class="para">
+ The <code class="systemitem">named</code> service is configured using the <code class="option">controls</code> statement in the <code class="filename">/etc/named.conf</code> configuration file as described in <a class="xref" href="#sec-bind-namedconf-state-other">Section 10.2.2.3, “Other Statement Types”</a>. Unless this statement is present, only the connections from the loopback address (<code class="systemitem">127.0.0.1</code>) will be allowed, and the key located in <code class="filename">/etc/rndc.key</code> will be used.
+ </div><div class="para">
+ For more information on this topic, refer to manual pages and the <em class="citetitle">BIND 9 Administrator Reference Manual</em> listed in <a class="xref" href="#sec-bind-additional-resources">Section 10.2.8, “Additional Resources”</a>.
+ </div><div class="important"><div class="admonition_header"><h2>Set the correct permissions</h2></div><div class="admonition"><div class="para">
+ To prevent unprivileged users from sending control commands to the service, make sure only <code class="systemitem">root</code> is allowed to read the <code class="filename">/etc/rndc.key</code> file:
+ </div><pre class="screen">~]# <code class="command">chmod o-rwx /etc/rndc.key</code></pre></div></div></div><div class="section" id="sec-bind-rndc-status"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.4.2. Checking the Service Status</h4></div></div></div><div class="para">
+ To check the current status of the <code class="systemitem">named</code> service, use the following command:
+ </div><pre class="screen">~]# <code class="command">rndc status</code>
+version: 9.7.0-P2-RedHat-9.7.0-5.P2.el6
+CPUs found: 1
+worker threads: 1
+number of zones: 16
+debug level: 0
+xfers running: 0
+xfers deferred: 0
+soa queries in progress: 0
+query logging is OFF
+recursive clients: 0/0/1000
+tcp clients: 0/100
+server is up and running</pre></div><div class="section" id="sec-bind-rndc-reload"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.4.3. Reloading the Configuration and Zones</h4></div></div></div><div class="para">
+ To reload both the configuration file and zones, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">rndc reload</code>
+server reload successful</pre><div class="para">
+ This will reload the zones while keeping all previously cached responses, so that you can make changes to the zone files without losing all stored name resolutions.
+ </div><div class="para">
+ To reload a single zone, specify its name after the <code class="command">reload</code> command, for example:
+ </div><pre class="screen">~]# <code class="command">rndc reload localhost</code>
+zone reload up-to-date</pre><div class="para">
+ Finally, to reload the configuration file and newly added zones only, type:
+ </div><pre class="screen">~]# <code class="command">rndc reconfig</code></pre><div class="note"><div class="admonition_header"><h2>Modifying zones with dynamic DNS</h2></div><div class="admonition"><div class="para">
+ If you intend to manually modify a zone that uses Dynamic <code class="systemitem">DNS</code> (DDNS), make sure you run the <code class="command">freeze</code> command first:
+ </div><pre class="screen">~]# <code class="command">rndc freeze localhost</code></pre><div class="para">
+ Once you are finished, run the <code class="command">thaw</code> command to allow the <code class="systemitem">DDNS</code> again and reload the zone:
+ </div><pre class="screen">~]# <code class="command">rndc thaw localhost</code>
+The zone reload and thaw was successful.</pre></div></div></div><div class="section" id="sec-bind-rndc-sign"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.4.4. Updating Zone Keys</h4></div></div></div><div class="para">
+ To update the DNSSEC keys and sign the zone, use the <code class="command">sign</code> command. For example:
+ </div><pre class="screen">~]# <code class="command">rndc sign localhost</code></pre><div class="para">
+ Note that to sign a zone with the above command, the <code class="option">auto-dnssec</code> option has to be set to <code class="literal">maintain</code> in the zone statement. For example:
+ </div><pre class="programlisting">zone "localhost" IN {
+ type master;
+ file "named.localhost";
+ allow-update { none; };
+ auto-dnssec maintain;
+};</pre></div><div class="section" id="sec-bind-rndc-validation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.4.5. Enabling the DNSSEC Validation</h4></div></div></div><div class="para">
+ To enable the DNSSEC validation, issue the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">rndc validation on</code></pre><div class="para">
+ Similarly, to disable this option, type:
+ </div><pre class="screen">~]# <code class="command">rndc validation off</code></pre><div class="para">
+ Refer to the <code class="option">options</code> statement described in <a class="xref" href="#sec-bind-namedconf-state">Section 10.2.2.2, “Common Statement Types”</a> for information on how to configure this option in <code class="filename">/etc/named.conf</code>.
+ </div></div><div class="section" id="sec-bind-rndc-querylog"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.4.6. Enabling the Query Logging</h4></div></div></div><div class="para">
+ To enable (or disable in case it is currently enabled) the query logging, issue the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">rndc querylog</code></pre><div class="para">
+ To check the current setting, use the <code class="command">status</code> command as described in <a class="xref" href="#sec-bind-rndc-status">Section 10.2.4.2, “Checking the Service Status”</a>.
+ </div></div></div><div class="section" id="sec-bind-dig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.5. Using the dig Utility</h3></div></div></div><a id="idm225480758048" class="indexterm"></a><div class="para">
+ The <code class="command">dig</code> utility is a command-line tool that allows you to perform <code class="systemitem">DNS</code> lookups and debug a nameserver configuration. Its typical usage is as follows:
+ </div><pre class="screen"><code class="command">dig</code> [@<em class="replaceable"><code>server</code></em>] [<em class="replaceable"><code>option</code></em>...] <em class="replaceable"><code>name</code></em> <em class="replaceable"><code>type</code></em></pre><div class="para">
+ Refer to <a class="xref" href="#sec-bind-zone-rr">Section 10.2.3.2, “Common Resource Records”</a> for a list of common values to use for <em class="replaceable"><code>type</code></em>.
+ </div><div class="section" id="sec-bind-dig-ns"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.5.1. Looking Up a Nameserver</h4></div></div></div><div class="para">
+ To look up a nameserver for a particular domain, use the command in the following form:
+ </div><pre class="screen"><code class="command">dig</code> <em class="replaceable"><code>name</code></em> NS</pre><div class="para">
+ In <a class="xref" href="#example-bind-dig-ns">Example 10.17, “A sample nameserver lookup”</a>, the <code class="command">dig</code> utility is used to display nameservers for <code class="systemitem">example.com</code>.
+ </div><div class="example" id="example-bind-dig-ns"><h6>Example 10.17. A sample nameserver lookup</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig example.com NS</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> example.com NS
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57883
+;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
+
+;; QUESTION SECTION:
+;example.com. IN NS
+
+;; ANSWER SECTION:
+example.com. 99374 IN NS a.iana-servers.net.
+example.com. 99374 IN NS b.iana-servers.net.
+
+;; Query time: 1 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:04:06 2010
+;; MSG SIZE rcvd: 77</pre></div></div><br class="example-break" /></div><div class="section" id="sec-bind-dig-a"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.5.2. Looking Up an IP Address</h4></div></div></div><div class="para">
+ To look up an <code class="systemitem">IP</code> address assigned to a particular domain, use the command in the following form:
+ </div><pre class="screen"><code class="command">dig</code> <em class="replaceable"><code>name</code></em> A</pre><div class="para">
+ In <a class="xref" href="#example-bind-dig-a">Example 10.18, “A sample IP address lookup”</a>, the <code class="command">dig</code> utility is used to display the <code class="systemitem">IP</code> address of <code class="systemitem">example.com</code>.
+ </div><div class="example" id="example-bind-dig-a"><h6>Example 10.18. A sample IP address lookup</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig example.com A</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> example.com A
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4849
+;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
+
+;; QUESTION SECTION:
+;example.com. IN A
+
+;; ANSWER SECTION:
+example.com. 155606 IN A 192.0.32.10
+
+;; AUTHORITY SECTION:
+example.com. 99175 IN NS a.iana-servers.net.
+example.com. 99175 IN NS b.iana-servers.net.
+
+;; Query time: 1 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:07:25 2010
+;; MSG SIZE rcvd: 93</pre></div></div><br class="example-break" /></div><div class="section" id="sec-bind-dig-x"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.5.3. Looking Up a Host Name</h4></div></div></div><div class="para">
+ To look up a host name for a particular <code class="systemitem">IP</code> address, use the command in the following form:
+ </div><pre class="screen"><code class="command">dig</code> <code class="option">-x</code> <em class="replaceable"><code>address</code></em></pre><div class="para">
+ In <a class="xref" href="#example-bind-dig-x">Example 10.19, “A Sample Host Name Lookup”</a>, the <code class="command">dig</code> utility is used to display the host name assigned to <code class="systemitem">192.0.32.10</code>.
+ </div><div class="example" id="example-bind-dig-x"><h6>Example 10.19. A Sample Host Name Lookup</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig -x 192.0.32.10</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> -x 192.0.32.10
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29683
+;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 6
+
+;; QUESTION SECTION:
+;10.32.0.192.in-addr.arpa. IN PTR
+
+;; ANSWER SECTION:
+10.32.0.192.in-addr.arpa. 21600 IN PTR www.example.com.
+
+;; AUTHORITY SECTION:
+32.0.192.in-addr.arpa. 21600 IN NS b.iana-servers.org.
+32.0.192.in-addr.arpa. 21600 IN NS c.iana-servers.net.
+32.0.192.in-addr.arpa. 21600 IN NS d.iana-servers.net.
+32.0.192.in-addr.arpa. 21600 IN NS ns.icann.org.
+32.0.192.in-addr.arpa. 21600 IN NS a.iana-servers.net.
+
+;; ADDITIONAL SECTION:
+a.iana-servers.net. 13688 IN A 192.0.34.43
+b.iana-servers.org. 5844 IN A 193.0.0.236
+b.iana-servers.org. 5844 IN AAAA 2001:610:240:2::c100:ec
+c.iana-servers.net. 12173 IN A 139.91.1.10
+c.iana-servers.net. 12173 IN AAAA 2001:648:2c30::1:10
+ns.icann.org. 12884 IN A 192.0.34.126
+
+;; Query time: 156 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:25:15 2010
+;; MSG SIZE rcvd: 310</pre></div></div><br class="example-break" /></div></div><div class="section" id="sec-bind-features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.6. Advanced Features of BIND</h3></div></div></div><div class="para">
+ Most BIND implementations only use the <code class="systemitem">named</code> service to provide name resolution services or to act as an authority for a particular domain. However, BIND version 9 has a number of advanced features that allow for a more secure and efficient <code class="systemitem">DNS</code> service.
+ </div><div class="important"><div class="admonition_header"><h2>Make sure the feature is supported</h2></div><div class="admonition"><div class="para">
+ Before attempting to use advanced features like DNSSEC, TSIG, or IXFR (Incremental Zone Transfer), make sure that the particular feature is supported by all nameservers in the network environment, especially when you use older versions of BIND or non-BIND servers.
+ </div></div></div><div class="para">
+ All of the features mentioned are discussed in greater detail in the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="#sec-bind-installed-docs">Section 10.2.8.1, “Installed Documentation”</a>.
+ </div><div class="section" id="sec-bind-features-views"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.6.1. Multiple Views</h4></div></div></div><a id="idm225445487072" class="indexterm"></a><div class="para">
+ Optionally, different information can be presented to a client depending on the network a request originates from. This is primarily used to deny sensitive <code class="systemitem">DNS</code> entries from clients outside of the local network, while allowing queries from clients inside the local network.
+ </div><div class="para">
+ To configure multiple views, add the <code class="command">view</code> statement to the <code class="filename">/etc/named.conf</code> configuration file. Use the <code class="option">match-clients</code> option to match <code class="systemitem">IP</code> addresses or entire networks and give them special options and zone data.
+ </div></div><div class="section" id="sec-bind-features-ixfr"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.6.2. Incremental Zone Transfers (IXFR)</h4></div></div></div><a id="idm225445293376" class="indexterm"></a><div class="para">
+ <em class="firstterm">Incremental Zone Transfers</em> (<em class="firstterm">IXFR</em>) allow a secondary nameserver to only download the updated portions of a zone modified on a primary nameserver. Compared to the standard transfer process, this makes the notification and update process much more efficient.
+ </div><a id="idm225439708768" class="indexterm"></a><div class="para">
+ Note that IXFR is only available when using dynamic updating to make changes to master zone records. If manually editing zone files to make changes, <em class="firstterm">Automatic Zone Transfer</em> (<em class="firstterm">AXFR</em>) is used.
+ </div></div><div class="section" id="sec-bind-features-tsig"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.6.3. Transaction SIGnatures (TSIG)</h4></div></div></div><a id="idm225434222784" class="indexterm"></a><div class="para">
+ <em class="firstterm">Transaction SIGnatures</em> (TSIG) ensure that a shared secret key exists on both primary and secondary nameservers before allowing a transfer. This strengthens the standard <code class="systemitem">IP</code> address-based method of transfer authorization, since attackers would not only need to have access to the <code class="systemitem">IP</code> address to transfer the zone, but they would also need to know the secret key.
+ </div><div class="para">
+ Since version 9, BIND also supports <em class="firstterm">TKEY</em>, which is another shared secret key method of authorizing zone transfers.
+ </div><div class="important"><div class="admonition_header"><h2>Secure the transfer</h2></div><div class="admonition"><div class="para">
+ When communicating over an insecure network, do not rely on <code class="systemitem">IP</code> address-based authentication only.
+ </div></div></div></div><div class="section" id="sec-bind-features-dnssec"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.6.4. DNS Security Extensions (DNSSEC)</h4></div></div></div><a id="idm225452786480" class="indexterm"></a><div class="para">
+ <em class="firstterm">Domain Name System Security Extensions</em> (<em class="firstterm">DNSSEC</em>) provide origin authentication of <code class="systemitem">DNS</code> data, authenticated denial of existence, and data integrity. When a particular domain is marked as secure, the <code class="literal">SERVFAIL</code> response is returned for each resource record that fails the validation.
+ </div><a id="idm225407642192" class="indexterm"></a><div class="para">
+ Note that to debug a DNSSEC-signed domain or a DNSSEC-aware resolver, you can use the <code class="command">dig</code> utility as described in <a class="xref" href="#sec-bind-dig">Section 10.2.5, “Using the dig Utility”</a>. Useful options are <code class="option">+dnssec</code> (requests DNSSEC-related resource records by setting the DNSSEC OK bit), <code class="option">+cd</code> (tells recursive nameserver not to validate the response), and <code class="option">+bufsize=512</code> (changes the packet size to 512B to get through some firewalls).
+ </div></div><div class="section" id="sec-bind-features-ipv6"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.6.5. Internet Protocol version 6 (IPv6)</h4></div></div></div><a id="idm225451357584" class="indexterm"></a><div class="para">
+ <em class="firstterm">Internet Protocol version 6</em> (<em class="firstterm">IPv6</em>) is supported through the use of <code class="option">AAAA</code> resource records, and the <code class="option">listen-on-v6</code> directive as described in <a class="xref" href="#table-bind-namedconf-common-options">Table 10.3, “Commonly Used Configuration Options”</a>.
+ </div></div></div><div class="section" id="sec-bind-mistakes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.7. Common Mistakes to Avoid</h3></div></div></div><a id="idm225434508048" class="indexterm"></a><div class="para">
+ The following is a list of recommendations on how to avoid common mistakes users make when configuring a nameserver:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Use semicolons and curly brackets correctly</span></dt><dd><div class="para">
+ An omitted semicolon or unmatched curly bracket in the <code class="filename">/etc/named.conf</code> file can prevent the <code class="systemitem">named</code> service from starting.
+ </div></dd><dt class="varlistentry"><span class="term">Use period (the <code class="literal">.</code> character) correctly</span></dt><dd><div class="para">
+ In zone files, a period at the end of a domain name denotes a fully qualified domain name. If omitted, the <code class="systemitem">named</code> service will append the name of the zone or the value of <code class="option">$ORIGIN</code> to complete it.
+ </div></dd><dt class="varlistentry"><span class="term">Increment the serial number when editing a zone file</span></dt><dd><div class="para">
+ If the serial number is not incremented, the primary nameserver will have the correct, new information, but the secondary nameservers will never be notified of the change, and will not attempt to refresh their data of that zone.
+ </div></dd><dt class="varlistentry"><span class="term">Configure the firewall</span></dt><dd><div class="para">
+ If a firewall is blocking connections from the <code class="systemitem">named</code> service to other nameservers, the recommended practice is to change the firewall settings.
+ </div><div class="warning" id="warning-Warning-Avoid_Using_Fixed_UDP_Source_Ports"><div class="admonition_header"><h2>Avoid using fixed UDP source ports</h2></div><div class="admonition"><div class="para">
+ Using a fixed <code class="systemitem">UDP</code> source port for <code class="systemitem">DNS</code> queries is a potential security vulnerability that could allow an attacker to conduct cache-poisoning attacks more easily. To prevent this, by default <code class="systemitem">DNS</code> sends from a random ephemeral port. Configure your firewall to allow outgoing queries from a random <code class="systemitem">UDP</code> source port. The range <code class="literal">1024</code> to <code class="literal">65535</code> is used by default.
+ </div></div></div></dd></dl></div></div><div class="section" id="sec-bind-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.8. Additional Resources</h3></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding BIND.
+ </div><div class="section" id="sec-bind-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.8.1. Installed Documentation</h4></div></div></div><a id="idm225463675872" class="indexterm"></a><div class="para">
+ BIND features a full range of installed documentation covering many different topics, each placed in its own subject directory. For each item below, replace <em class="replaceable"><code>version</code></em> with the version of the <span class="package">bind</span> package installed on the system:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/</code> </span></dt><dd><div class="para">
+ The main directory containing the most recent documentation. The directory contains the <em class="citetitle">BIND 9 Administrator Reference Manual</em> in HTML and PDF formats, which details BIND resource requirements, how to configure different types of nameservers, how to perform load balancing, and other advanced topics.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/sample/etc/</code> </span></dt><dd><div class="para">
+ The directory containing examples of <code class="systemitem">named</code> configuration files.
+ </div></dd></dl></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="filename">rndc(8)</code> </span></dt><dd><div class="para">
+ The manual page for the <code class="command">rndc</code> name server control utility, containing documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">named(8)</code> </span></dt><dd><div class="para">
+ The manual page for the Internet domain name server <code class="systemitem">named</code>, containing documentation on assorted arguments that can be used to control the BIND nameserver daemon.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">lwresd(8)</code> </span></dt><dd><div class="para">
+ The manual page for the lightweight resolver daemon <code class="systemitem">lwresd</code>, containing documentation on the daemon and its usage.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">named.conf(5)</code> </span></dt><dd><div class="para">
+ The manual page with a comprehensive list of options available within the <code class="systemitem">named</code> configuration file.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">rndc.conf(5)</code> </span></dt><dd><div class="para">
+ The manual page with a comprehensive list of options available within the <code class="command">rndc</code> configuration file.
+ </div></dd></dl></div></div><div class="section" id="sec-bind-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.8.2. Useful Websites</h4></div></div></div><a id="idm225447043088" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a href="http://www.isc.org/software/bind">http://www.isc.org/software/bind</a> </span></dt><dd><div class="para">
+ The home page of the BIND project containing information about current releases as well as a PDF version of the <em class="citetitle">BIND 9 Administrator Reference Manual</em>.
+ </div></dd></dl></div></div><div class="section" id="sec-bind-related-books"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.8.3. Related Books</h4></div></div></div><a id="idm225447882080" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><em class="citetitle">DNS and BIND</em> by Paul Albitz and Cricket Liu; O'Reilly & Associates</span></dt><dd><div class="para">
+ A popular reference that explains both common and esoteric BIND configuration options, and provides strategies for securing a DNS server.
+ </div></dd><dt class="varlistentry"><span class="term"><em class="citetitle">The Concise Guide to DNS and BIND</em> by Nicolai Langfeldt; Que</span></dt><dd><div class="para">
+ Looks at the connection between multiple network services and BIND, with an emphasis on task-oriented, technical topics.
+ </div></dd></dl></div></div></div></div></div></div><div xml:lang="en-US" class="appendix" id="app-Revision_History" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
+ <div class="revhistory"><table summary="Revision History"><tr><th align="left" valign="top" colspan="3"><strong>Revision History</strong></th></tr><tr><td align="left">Revision 2-0</td><td align="left">Tues Jan 6 2015</td><td align="left"><span class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td> Update for Fedora 21. </td></tr></table>
+
+ </td></tr><tr><td align="left">Revision 1-1.2</td><td align="left">Mon Jan 5 2015</td><td align="left"><span class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td> General update and corrections for Fedora 20. </td></tr></table>
+
+ </td></tr><tr><td align="left">Revision 1-1</td><td align="left">Fri Aug 1 2014</td><td align="left"><span class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td> First version of the Fedora Networking Guide. </td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div><div class="index" id="idm225489704480"><div class="titlepage"><div><div><h1 class="title">Index</h1></div></div></div><div class="index"><div class="indexdiv"><h3>Symbols</h3><dl><dt>/etc/named.conf (see BIND)</dt><dt> /etc/sysconfig/dhcpd , <a class="indexterm" href="#idm225408573744">Starting and Stopping the Server</a></dt></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>authoritative nameserver (see BIND)</dt></dl></div><div class="indexdiv"><h3>B</h3><dl><dt>Berkeley Internet Name Domain (see BIND)</dt><dt>BIND</dt><dd><dl><dt>additional resources</dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#sec-bind-installed-docs">Installed Documentation</a></dt><dt>related books, <a class="indexterm" href="#sec-bind-related-books">Related Books</a></dt><dt>useful websites, <a class="indexterm" href="#sec-bind-useful-websites">Useful Websites</a></dt></dl></dd><dt>common mistakes, <a class="indexterm" href="#sec-bind-mistakes">Common Mistakes to
Avoid</a></dt><dt>configuration</dt><dd><dl><dt>acl statement, <a class="indexterm" href="#sec-bind-namedconf-state">Common Statement Types</a></dt><dt>comment tags, <a class="indexterm" href="#sec-bind-namedconf-comm">Comment Tags</a></dt><dt>controls statement, <a class="indexterm" href="#sec-bind-namedconf-state-other">Other Statement Types</a></dt><dt>include statement, <a class="indexterm" href="#sec-bind-namedconf-state">Common Statement Types</a></dt><dt>key statement, <a class="indexterm" href="#sec-bind-namedconf-state-other">Other Statement Types</a></dt><dt>logging statement, <a class="indexterm" href="#sec-bind-namedconf-state-other">Other Statement Types</a></dt><dt>options statement, <a class="indexterm" href="#sec-bind-namedconf-state">Common Statement Types</a></dt><dt>server statement, <a class="indexterm" href="#sec-bind-namedconf-state-other">Other Statement Types</a></dt><dt>trusted-keys statement, <a class="indexterm" href="#sec-bind-namedconf-state-oth
er">Other Statement Types</a></dt><dt>view statement, <a class="indexterm" href="#sec-bind-namedconf-state-other">Other Statement Types</a></dt><dt>zone statement, <a class="indexterm" href="#sec-bind-namedconf-state">Common Statement Types</a></dt></dl></dd><dt>directories</dt><dd><dl><dt>/etc/named/, <a class="indexterm" href="#sec-bind-namedconf">Configuring the named Service</a></dt><dt>/var/named/, <a class="indexterm" href="#sec-bind-zone">Editing Zone Files</a></dt><dt>/var/named/data/, <a class="indexterm" href="#sec-bind-zone">Editing Zone Files</a></dt><dt>/var/named/dynamic/, <a class="indexterm" href="#sec-bind-zone">Editing Zone Files</a></dt><dt>/var/named/slaves/, <a class="indexterm" href="#sec-bind-zone">Editing Zone Files</a></dt></dl></dd><dt>features</dt><dd><dl><dt>Automatic Zone Transfer (AXFR), <a class="indexterm" href="#sec-bind-features-ixfr">Incremental Zone Transfers (IXFR)</a></dt><dt>DNS Security Extensions (DNSSEC), <a class="indexterm" href="#
sec-bind-features-dnssec">DNS Security Extensions (DNSSEC)</a></dt><dt>Incremental Zone Transfer (IXFR), <a class="indexterm" href="#sec-bind-features-ixfr">Incremental Zone Transfers (IXFR)</a></dt><dt>Internet Protocol version 6 (IPv6), <a class="indexterm" href="#sec-bind-features-ipv6">Internet Protocol version 6 (IPv6)</a></dt><dt>multiple views, <a class="indexterm" href="#sec-bind-features-views">Multiple Views</a></dt><dt>Transaction SIGnature (TSIG), <a class="indexterm" href="#sec-bind-features-tsig">Transaction SIGnatures (TSIG)</a></dt></dl></dd><dt>files</dt><dd><dl><dt>/etc/named.conf, <a class="indexterm" href="#sec-bind-namedconf">Configuring the named Service</a>, <a class="indexterm" href="#sec-bind-rndc-configuration">Configuring the Utility</a></dt><dt>/etc/rndc.conf, <a class="indexterm" href="#sec-bind-rndc-configuration">Configuring the Utility</a></dt><dt>/etc/rndc.key, <a class="indexterm" href="#sec-bind-rndc-configuration">Configuring the Utility</
a></dt></dl></dd><dt>resource record, <a class="indexterm" href="#sec-dns-introduction-zones">Nameserver Zones</a></dt><dt>types</dt><dd><dl><dt>authoritative nameserver, <a class="indexterm" href="#sec-dns-introduction-nameservers">Nameserver Types</a></dt><dt>primary (master) nameserver, <a class="indexterm" href="#sec-dns-introduction-zones">Nameserver Zones</a>, <a class="indexterm" href="#sec-dns-introduction-nameservers">Nameserver Types</a></dt><dt>recursive nameserver, <a class="indexterm" href="#sec-dns-introduction-nameservers">Nameserver Types</a></dt><dt>secondary (slave) nameserver, <a class="indexterm" href="#sec-dns-introduction-zones">Nameserver Zones</a>, <a class="indexterm" href="#sec-dns-introduction-nameservers">Nameserver Types</a></dt></dl></dd><dt>utilities</dt><dd><dl><dt>dig, <a class="indexterm" href="#sec-dns-introduction-bind">BIND as a Nameserver</a>, <a class="indexterm" href="#sec-bind-dig">Using the dig Utility</a>, <a class="indexterm" href=
"#sec-bind-features-dnssec">DNS Security Extensions (DNSSEC)</a></dt><dt>named, <a class="indexterm" href="#sec-dns-introduction-bind">BIND as a Nameserver</a>, <a class="indexterm" href="#sec-bind-namedconf">Configuring the named Service</a></dt><dt>rndc, <a class="indexterm" href="#sec-dns-introduction-bind">BIND as a Nameserver</a>, <a class="indexterm" href="#sec-bind-rndc">Using the rndc Utility</a></dt></dl></dd><dt>zones</dt><dd><dl><dt>$INCLUDE directive, <a class="indexterm" href="#sec-bind-zone-directives">Common Directives</a></dt><dt>$ORIGIN directive, <a class="indexterm" href="#sec-bind-zone-directives">Common Directives</a></dt><dt>$TTL directive, <a class="indexterm" href="#sec-bind-zone-directives">Common Directives</a></dt><dt>A (Address) resource record, <a class="indexterm" href="#sec-bind-zone-rr">Common Resource Records</a></dt><dt>CNAME (Canonical Name) resource record, <a class="indexterm" href="#sec-bind-zone-rr">Common Resource Records</a></dt><dt>c
omment tags, <a class="indexterm" href="#sec-bind-zone-comm">Comment Tags</a></dt><dt>description, <a class="indexterm" href="#sec-dns-introduction-zones">Nameserver Zones</a></dt><dt>example usage, <a class="indexterm" href="#sec-bind-zone-examples-basic">A Simple Zone File</a>, <a class="indexterm" href="#sec-bind-configuration-zone-reverse">A Reverse Name Resolution Zone File</a></dt><dt>MX (Mail Exchange) resource record, <a class="indexterm" href="#sec-bind-zone-rr">Common Resource Records</a></dt><dt>NS (Nameserver) resource record, <a class="indexterm" href="#sec-bind-zone-rr">Common Resource Records</a></dt><dt>PTR (Pointer) resource record, <a class="indexterm" href="#sec-bind-zone-rr">Common Resource Records</a></dt><dt>SOA (Start of Authority) resource record, <a class="indexterm" href="#sec-bind-zone-rr">Common Resource Records</a></dt></dl></dd></dl></dd><dt>bonding (see channel bonding)</dt></dl></div><div class="indexdiv"><h3>C</h3><dl><dt>channel bonding</dt>
<dd><dl><dt>configuration, <a class="indexterm" href="#sec-Using_Channel_Bonding">Using Channel Bonding</a></dt><dt>description, <a class="indexterm" href="#sec-Using_Channel_Bonding">Using Channel Bonding</a></dt><dt>parameters to bonded interfaces, <a class="indexterm" href="#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>channel bonding interface (see kernel module)</dt></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>default gateway, <a class="indexterm" href="#sec-Static-Routes_and_the_Default_Gateway">Static Routes and the Default Gateway</a></dt><dt>DHCP, <a class="indexterm" href="#ch-DHCP_Servers">DHCP Servers</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="#sec-dhcp-additional-resources">Additional Resources</a></dt><dt>command-line options, <a class="indexterm" href="#idm225408573744">Starting and Stopping the Server</a></dt><dt>dhcpd.conf, <a class="indexterm" href="#config-file">Configuration File</a></dt><d
t>dhcpd.leases, <a class="indexterm" href="#idm225408573744">Starting and Stopping the Server</a></dt><dt>dhcpd6.conf, <a class="indexterm" href="#sec-dhcp_for_ipv6_dhcpv6">DHCP for IPv6 (DHCPv6)</a></dt><dt>DHCPv6, <a class="indexterm" href="#sec-dhcp_for_ipv6_dhcpv6">DHCP for IPv6 (DHCPv6)</a></dt><dt>dhcrelay, <a class="indexterm" href="#dhcp-relay-agent">DHCP Relay Agent</a></dt><dt>global parameters, <a class="indexterm" href="#config-file">Configuration File</a></dt><dt>group, <a class="indexterm" href="#config-file">Configuration File</a></dt><dt>options, <a class="indexterm" href="#config-file">Configuration File</a></dt><dt>reasons for using, <a class="indexterm" href="#sec-dhcp-why">Why Use DHCP?</a></dt><dt>Relay Agent, <a class="indexterm" href="#dhcp-relay-agent">DHCP Relay Agent</a></dt><dt>server configuration, <a class="indexterm" href="#sec-dhcp-configuring-server">Configuring a DHCP Server</a></dt><dt>shared-network, <a class="indexterm" href="#config-file"
>Configuration File</a></dt><dt>starting the server, <a class="indexterm" href="#idm225408573744">Starting and Stopping the Server</a></dt><dt>stopping the server, <a class="indexterm" href="#idm225408573744">Starting and Stopping the Server</a></dt><dt>subnet, <a class="indexterm" href="#config-file">Configuration File</a></dt></dl></dd><dt>dhcpd.conf, <a class="indexterm" href="#config-file">Configuration File</a></dt><dt>dhcpd.leases, <a class="indexterm" href="#idm225408573744">Starting and Stopping the Server</a></dt><dt>dhcrelay, <a class="indexterm" href="#dhcp-relay-agent">DHCP Relay Agent</a></dt><dt>dig (see BIND)</dt><dt>DNS</dt><dd><dl><dt>definition, <a class="indexterm" href="#ch-DNS_Servers">DNS Servers</a></dt><dd><dl><dt>(see also BIND)</dt></dl></dd></dl></dd><dt>Dynamic Host Configuration Protocol (see DHCP)</dt></dl></div><div class="indexdiv"><h3>F</h3><dl><dt>feedback</dt><dd><dl><dt>contact information for this manual, <a class="indexterm" href="#sec-P
reface-Feedback">Feedback</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>K</h3><dl><dt>kernel module</dt><dd><dl><dt>bonding module, <a class="indexterm" href="#sec-Using_Channel_Bonding">Using Channel Bonding</a></dt><dd><dl><dt>description, <a class="indexterm" href="#sec-Using_Channel_Bonding">Using Channel Bonding</a></dt><dt>parameters to bonded interfaces, <a class="indexterm" href="#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>module parameters</dt><dd><dl><dt>bonding module parameters, <a class="indexterm" href="#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd></dl></dd></dl></div><div class="indexdiv"><h3>M</h3><dl><dt>Multihomed DHCP</dt><dd><dl><dt>host configuration, <a class="indexterm" href="#sec-dns_Host_Configuration">Host Configuration</a></dt><dt>server configuration, <a class="indexterm" href="#sec-Configuring_a_Multihomed_DHCP_Server">Configuring a Multihomed DHCP Server</a></dt></dl></d
d></dl></div><div class="indexdiv"><h3>N</h3><dl><dt>named (see BIND)</dt><dt>nameserver (see DNS)</dt><dt>NIC</dt><dd><dl><dt>binding into single channel, <a class="indexterm" href="#sec-Using_Channel_Bonding">Using Channel Bonding</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>primary nameserver (see BIND)</dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>recursive nameserver (see BIND)</dt><dt>resource record (see BIND)</dt><dt>rndc (see BIND)</dt><dt>root nameserver (see BIND)</dt></dl></div><div class="indexdiv"><h3>S</h3><dl><dt>secondary nameserver (see BIND)</dt><dt>static route, <a class="indexterm" href="#sec-Static-Routes_and_the_Default_Gateway">Static Routes and the Default Gateway</a></dt></dl></div></div></div></div></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/css/common.css b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..d7dc3f2
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/css/common.css
@@ -0,0 +1,1528 @@
+* {
+ widows: 2 !important;
+ orphans: 2 !important;
+}
+
+body, h1, h2, h3, h4, h5, h6, pre, li, div {
+ line-height: 1.29em;
+}
+
+body {
+ background-color: white;
+ margin:0 auto;
+ font-family: "liberation sans", "Myriad ", "Bitstream Vera Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS", helvetica, verdana, arial, sans-serif;
+ font-size:12px;
+ max-width:55em;
+ color:black;
+}
+
+body.toc_embeded {
+ /*for web hosting system only*/
+ margin-left: 300px;
+}
+
+object.toc, iframe.toc {
+ /*for web hosting system only*/
+ border-style:none;
+ position:fixed;
+ width:290px;
+ height:99.99%;
+ top:0;
+ left:0;
+ z-index: 100;
+ border-style:none;
+ border-right:1px solid #999;
+}
+
+/* Hide web menu */
+
+body.notoc {
+ margin-left: 3em;
+}
+
+iframe.notoc {
+ border-style:none;
+ border: none;
+ padding: 0em;
+ position:fixed;
+ width: 21px;
+ height: 29px;
+ top: 0px;
+ left:0;
+ overflow: hidden;
+ margin: 0em;
+ margin-left: -3px;
+}
+/* End hide web menu */
+
+/* desktop styles */
+body.desktop {
+ margin-left: 26em;
+}
+
+body.desktop .book > .toc {
+ display:block;
+ width:24em;
+ height:99%;
+ position:fixed;
+ overflow:auto;
+ top:0px;
+ left:0px;
+ padding-left:1em;
+ background-color:#EEEEEE;
+}
+
+.toc {
+ line-height:1.35em;
+}
+
+.toc .glossary,
+.toc .chapter, .toc .appendix {
+ margin-top:1em;
+}
+
+.toc .part {
+ margin-top:1em;
+ display:block;
+}
+
+span.glossary,
+span.appendix {
+ display:block;
+ margin-top:0.5em;
+}
+
+div {
+ padding-top:0px;
+}
+
+div.section {
+ padding-top:1em;
+}
+
+p, div.para, div.formalpara {
+ padding-top:0px;
+ margin-top:0.3em;
+ padding-bottom:0px;
+ margin-bottom:1em;
+}
+
+/*Links*/
+a {
+ outline: none;
+}
+
+a:link {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#3366cc;
+}
+
+a:visited {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#003366;
+}
+
+div.longdesc-link {
+ float:right;
+ color:#999;
+}
+
+.toc a, .qandaset a {
+ font-weight:normal;
+ border:none;
+}
+
+.toc a:hover, .qandaset a:hover
+{
+ border-bottom: 1px dotted;
+}
+
+/*headings*/
+h1, h2, h3, h4, h5, h6 {
+ color: #336699;
+ margin-top: 0em;
+ margin-bottom: 0em;
+ background-color: transparent;
+ page-break-inside: avoid;
+ page-break-after: avoid;
+}
+
+h1 {
+ font-size:2.0em;
+}
+
+.titlepage h1.title {
+ font-size: 3.0em;
+ padding-top: 1em;
+ text-align:left;
+}
+
+.book > .titlepage h1.title {
+ text-align:center;
+}
+
+.article > .titlepage h1.title {
+ text-align:center;
+}
+
+.set .titlepage > div > div > h1.title {
+ text-align:center;
+}
+
+.producttitle {
+ margin-top: 0em;
+ margin-bottom: 0em;
+ font-size: 3.0em;
+ font-weight: bold;
+ background: #003d6e url(../images/h1-bg.png) top left repeat-x;
+ color: white;
+ text-align: center;
+ padding: 0.7em;
+}
+
+.titlepage .corpauthor {
+ margin-top: 1em;
+ text-align: center;
+}
+
+.section h1.title {
+ font-size: 1.6em;
+ padding: 0em;
+ color: #336699;
+ text-align: left;
+ background: white;
+}
+
+h2 {
+ font-size:1.6em;
+}
+
+
+h2.subtitle, h3.subtitle {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ text-align: center;
+}
+
+.preface > div > div > div > h2.title {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+.appendix h2 {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+
+
+h3 {
+ font-size:1.3em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+h4 {
+ font-size:1.1em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h5 {
+ font-size:1em;
+}
+
+h6 {
+ font-size:1em;
+}
+
+h5.formalpara {
+ font-size:1em;
+ margin-top:2em;
+ margin-bottom:.8em;
+}
+
+.abstract h6 {
+ margin-top:1em;
+ margin-bottom:.5em;
+ font-size:2em;
+}
+
+/*element rules*/
+hr {
+ border-collapse: collapse;
+ border-style:none;
+ border-top: 1px dotted #ccc;
+ width:100%;
+ margin-top: 3em;
+}
+
+/* web site rules */
+ul.languages, .languages li {
+ display:inline;
+ padding:0em;
+}
+
+.languages li a {
+ padding:0em .5em;
+ text-decoration: none;
+}
+
+.languages li p, .languages li div.para {
+ display:inline;
+}
+
+.languages li a:link, .languages li a:visited {
+ color:#444;
+}
+
+.languages li a:hover, .languages li a:focus, .languages li a:active {
+ color:black;
+}
+
+ul.languages {
+ display:block;
+ background-color:#eee;
+ padding:.5em;
+}
+
+/*supporting stylesheets*/
+
+/*unique to the webpage only*/
+.books {
+ position:relative;
+}
+
+.versions li {
+ width:100%;
+ clear:both;
+ display:block;
+}
+
+a.version {
+ font-size:2em;
+ text-decoration:none;
+ width:100%;
+ display:block;
+ padding:1em 0em .2em 0em;
+ clear:both;
+}
+
+a.version:before {
+ content:"Version";
+ font-size:smaller;
+}
+
+a.version:visited, a.version:link {
+ color:#666;
+}
+
+a.version:focus, a.version:hover {
+ color:black;
+}
+
+.books {
+ display:block;
+ position:relative;
+ clear:both;
+ width:100%;
+}
+
+.books li {
+ display:block;
+ width:200px;
+ float:left;
+ position:relative;
+ clear: none ;
+}
+
+.books .html {
+ width:170px;
+ display:block;
+}
+
+.books .pdf {
+ position:absolute;
+ left:170px;
+ top:0px;
+ font-size:smaller;
+}
+
+.books .pdf:link, .books .pdf:visited {
+ color:#555;
+}
+
+.books .pdf:hover, .books .pdf:focus {
+ color:#000;
+}
+
+.books li a {
+ text-decoration:none;
+}
+
+.books li a:hover {
+ color:black;
+}
+
+/*products*/
+.products li {
+ display: block;
+ width:300px;
+ float:left;
+}
+
+.products li a {
+ width:300px;
+ padding:.5em 0em;
+}
+
+.products ul {
+ clear:both;
+}
+
+/*revision history*/
+.revhistory {
+ display:block;
+}
+
+.revhistory table {
+ background-color:transparent;
+ border-color:#fff;
+ padding:0em;
+ margin: 0;
+ border-collapse:collapse;
+ border-style:none;
+}
+
+.revhistory td {
+ text-align :left;
+ padding:0em;
+ border: none;
+ border-top: 1px solid #fff;
+ font-weight: bold;
+}
+
+.revhistory .simplelist td {
+ font-weight: normal;
+}
+
+.revhistory .simplelist {
+ margin-bottom: 1.5em;
+ margin-left: 1em;
+}
+
+.revhistory table th {
+ display: none;
+}
+
+
+/*credits*/
+.authorgroup div {
+ clear:both;
+ text-align: center;
+}
+
+h3.author {
+ margin: 0em;
+ padding: 0em;
+ padding-top: 1em;
+}
+
+.authorgroup h4 {
+ padding: 0em;
+ margin: 0em;
+ padding-top: 1em;
+ margin-top: 1em;
+}
+
+.author,
+.editor,
+.translator,
+.othercredit,
+.contrib {
+ display: block;
+}
+
+.revhistory .author {
+ display: inline;
+}
+
+.othercredit h3 {
+ padding-top: 1em;
+}
+
+
+.othercredit {
+ margin:0em;
+ padding:0em;
+}
+
+.releaseinfo {
+ clear: both;
+}
+
+.copyright {
+ margin-top: 1em;
+}
+
+/* qanda sets */
+.answer {
+ margin-bottom:1em;
+ border-bottom:1px dotted #ccc;
+}
+
+.qandaset .toc {
+ border-bottom:1px dotted #ccc;
+}
+
+.question {
+ font-weight:bold;
+}
+
+.answer .data, .question .data {
+ padding-left: 2.6em;
+}
+
+.answer label, .question label {
+ float:left;
+ font-weight:bold;
+}
+
+/* inline syntax highlighting */
+.perl_Alert {
+ color: #0000ff;
+}
+
+.perl_BaseN {
+ color: #007f00;
+}
+
+.perl_BString {
+ color: #5C3566;
+}
+
+.perl_Char {
+ color: #ff00ff;
+}
+
+.perl_Comment {
+ color: #FF00FF;
+}
+
+
+.perl_DataType {
+ color: #0000ff;
+}
+
+
+.perl_DecVal {
+ color: #00007f;
+}
+
+
+.perl_Error {
+ color: #ff0000;
+}
+
+
+.perl_Float {
+ color: #00007f;
+}
+
+
+.perl_Function {
+ color: #007f00;
+}
+
+
+.perl_IString {
+ color: #5C3566;
+}
+
+
+.perl_Keyword {
+ color: #002F5D;
+}
+
+
+.perl_Operator {
+ color: #ffa500;
+}
+
+
+.perl_Others {
+ color: #b03060;
+}
+
+
+.perl_RegionMarker {
+ color: #96b9ff;
+}
+
+
+.perl_Reserved {
+ color: #9b30ff;
+}
+
+
+.perl_String {
+ color: #5C3566;
+}
+
+
+.perl_Variable {
+ color: #0000ff;
+}
+
+
+.perl_Warning {
+ color: #0000ff;
+}
+
+/*Lists*/
+ul {
+ padding-left:1.6em;
+ list-style-image:url(../images/dot.png);
+ list-style-type: circle;
+}
+
+ul ul {
+ list-style-image:url(../images/dot2.png);
+ list-style-type: circle;
+}
+
+ol {
+ list-style-image:none;
+ list-style-type: decimal;
+}
+
+ol ol {
+ list-style-type: lower-alpha;
+}
+
+ol.arabic {
+ list-style-type: decimal;
+}
+
+ol.loweralpha {
+ list-style-type: lower-alpha;
+}
+
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+dt {
+ font-weight:bold;
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+dd {
+ margin:0em;
+ margin-left:2em;
+ padding-top:0em;
+ padding-bottom: 1em;
+}
+
+li {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.4em;
+}
+
+li p, li div.para {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.3em;
+}
+
+/*images*/
+img {
+ display:block;
+ margin: 2em 0;
+}
+
+.inlinemediaobject, .inlinemediaobject img {
+ display:inline;
+ margin:0em;
+}
+
+.figure img {
+ display:block;
+ margin:0;
+ page-break-inside: avoid;
+}
+
+.figure .title {
+ margin:0em;
+ margin-bottom:2em;
+ padding:0px;
+}
+
+/*document modes*/
+.confidential {
+ background-color:#900;
+ color:White;
+ padding:.5em .5em;
+ text-transform:uppercase;
+ text-align:center;
+}
+
+.longdesc-link {
+ display:none;
+}
+
+.longdesc {
+ display:none;
+}
+
+.prompt {
+ padding:0em .3em;
+}
+
+/*user interface styles*/
+.screen .replaceable {
+}
+
+.guibutton, .guilabel {
+ font-family: "liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight: bold;
+ white-space: nowrap;
+}
+
+.example {
+ background-color: #ffffff;
+ border-left: 3px solid #aaaaaa;
+ padding-top: 1em;
+ padding-bottom: 0.1em;
+}
+
+.example h6 {
+ padding-left: 10px;
+}
+
+.example-contents {
+ padding-left: 10px;
+ background-color: #ffffff;
+}
+
+.example-contents .para {
+/* padding: 10px;*/
+}
+
+/*terminal/console text*/
+.computeroutput,
+.option {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+.replaceable {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-style: italic;
+}
+
+.command, .filename, .keycap, .classname, .literal {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+/* no bold in toc */
+.toc * {
+ font-weight: inherit;
+}
+
+pre {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ display:block;
+ background-color: #f5f5f5;
+ color: #000000;
+ border: 1px solid #aaaaaa;
+ margin-bottom: 0.3em;
+ padding:.5em 1em;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+ font-size: 0.9em;
+}
+
+pre .replaceable,
+pre .keycap {
+}
+
+code {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+/* white-space: nowrap;*/
+ white-space: pre-wrap;
+ word-wrap: break-word;
+ font-weight:bold;
+}
+
+.parameter code {
+ display: inline;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+}
+
+/*Notifications*/
+div.warning:before {
+ content:url(../images/warning.png);
+ padding-left: 5px;
+}
+
+div.note:before {
+ content:url(../images/note.png);
+ padding-left: 5px;
+}
+
+div.important:before {
+ content:url(../images/important.png);
+ padding-left: 5px;
+}
+
+div.warning, div.note, div.important {
+ color: black;
+ margin: 0em;
+ padding: 0em;
+ background: none;
+ background-color: white;
+ margin-bottom: 1em;
+ border-bottom: 1px solid #aaaaaa;
+ page-break-inside: avoid;
+}
+
+div.warning h2, div.note h2,div.important h2 {
+ margin: 0em;
+ padding: 0em;
+ color: #eeeeec;
+ padding-top: 0px;
+ padding-bottom: 0px;
+ height: 1.4em;
+ line-height: 1.4em;
+ font-size: 1.4em;
+ display:inline;
+}
+
+div.admonition_header {
+ clear: both;
+ margin: 0em;
+ padding: 0em;
+ margin-top: -3.3em;
+ padding-left: 58px;
+ line-height: 1.0em;
+ font-size: 1.0em;
+}
+
+div.warning div.admonition_header {
+ background: url(../images/red.png) top left repeat-x;
+ background-color: #590000;
+}
+
+div.note div.admonition_header {
+ background: url(../images/green.png) top right repeat-x;
+ background-color: #597800;
+}
+
+div.important div.admonition_header {
+ background: url(../images/yellow.png) top right repeat-x;
+ background-color: #a6710f;
+}
+
+div.warning p, div.warning div.para,
+div.note p, div.note div.para,
+div.important p, div.important div.para {
+ padding: 0em;
+ margin: 0em;
+}
+
+div.admonition {
+ border: none;
+ border-left: 1px solid #aaaaaa;
+ border-right: 1px solid #aaaaaa;
+ padding:0em;
+ margin:0em;
+ padding-top: 1.5em;
+ padding-bottom: 1em;
+ padding-left: 2em;
+ padding-right: 1em;
+ background-color: #eeeeec;
+ -moz-border-radius: 0px;
+ -webkit-border-radius: 0px;
+ border-radius: 0px;
+}
+
+/*Page Title*/
+#title {
+ display:block;
+ height:45px;
+ padding-bottom:1em;
+ margin:0em;
+}
+
+#title a.left{
+ display:inline;
+ border:none;
+}
+
+#title a.left img{
+ border:none;
+ float:left;
+ margin:0em;
+ margin-top:.7em;
+}
+
+#title a.right {
+ padding-bottom:1em;
+}
+
+#title a.right img {
+ border:none;
+ float:right;
+ margin:0em;
+ margin-top:.7em;
+}
+
+/*Table*/
+div.table {
+ page-break-inside: avoid;
+}
+
+table {
+ border:1px solid #6c614b;
+ width:100%;
+ border-collapse:collapse;
+}
+
+table.simplelist, .calloutlist table {
+ border-style: none;
+}
+
+table th {
+ text-align:left;
+ background-color:#6699cc;
+ padding:.3em .5em;
+ color:white;
+}
+
+table td {
+ padding:.15em .5em;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+table th p:first-child, table td p:first-child, table li p:first-child,
+table th div.para:first-child, table td div.para:first-child, table li div.para:first-child {
+ margin-top:0em;
+ padding-top:0em;
+ display:inline;
+}
+
+th, td {
+ border-style:none;
+ vertical-align: top;
+ border: 1px solid #000;
+}
+
+.simplelist th, .simplelist td {
+ border: none;
+}
+
+table table td {
+ border-bottom:1px dotted #aaa;
+ background-color:white;
+ padding:.6em 0em;
+}
+
+table table {
+ border:1px solid white;
+}
+
+td.remarkval {
+ color:#444;
+}
+
+td.fieldval {
+ font-weight:bold;
+}
+
+.lbname, .lbtype, .lbdescr, .lbdriver, .lbhost {
+ color:white;
+ font-weight:bold;
+ background-color:#999;
+ width:120px;
+}
+
+td.remarkval {
+ width:230px;
+}
+
+td.tname {
+ font-weight:bold;
+}
+
+th.dbfield {
+ width:120px;
+}
+
+th.dbtype {
+ width:70px;
+}
+
+th.dbdefault {
+ width:70px;
+}
+
+th.dbnul {
+ width:70px;
+}
+
+th.dbkey {
+ width:70px;
+}
+
+span.book {
+ margin-top:4em;
+ display:block;
+ font-size:11pt;
+}
+
+span.book a{
+ font-weight:bold;
+}
+span.chapter {
+ display:block;
+ margin-top:0.5em;
+}
+
+table.simplelist td, .calloutlist table td {
+ border-style: none;
+}
+
+/*Breadcrumbs*/
+#breadcrumbs ul li.first:before {
+ content:" ";
+}
+
+#breadcrumbs {
+ color:#900;
+ padding:3px;
+ margin-bottom:25px;
+}
+
+#breadcrumbs ul {
+ margin-left:0;
+ padding-left:0;
+ display:inline;
+ border:none;
+}
+
+#breadcrumbs ul li {
+ margin-left:0;
+ padding-left:2px;
+ border:none;
+ list-style:none;
+ display:inline;
+}
+
+#breadcrumbs ul li:before {
+ content:"\0020 \0020 \0020 \00BB \0020";
+ color:#333;
+}
+
+/*index*/
+.glossary h3,
+.index h3 {
+ font-size: 2em;
+ color:#aaa;
+ margin:0em;
+}
+
+.indexdiv {
+ margin-bottom:1em;
+}
+
+.glossary dt,
+.index dt {
+ color:#444;
+ padding-top:.5em;
+}
+
+.glossary dl dl dt,
+.index dl dl dt {
+ color:#777;
+ font-weight:normal;
+ padding-top:0em;
+}
+
+.index dl dl dt:before {
+ content:"- ";
+ color:#ccc;
+}
+
+/*changes*/
+.footnote {
+ font-size: .7em;
+ margin:0em;
+ color:#222;
+}
+
+table .footnote {
+}
+
+sup {
+ color:#999;
+ margin:0em;
+ padding:0em;
+ line-height: .4em;
+ font-size: 1em;
+ padding-left:0em;
+}
+
+.footnote {
+ position:relative;
+}
+
+.footnote sup {
+ color:#e3dcc0;
+ position:absolute;
+ left: .4em;
+}
+
+.footnote sup a:link,
+.footnote sup a:visited {
+ color:#92917d;
+ text-decoration:none;
+}
+
+.footnote:hover sup a {
+ text-decoration:none;
+}
+
+.footnote p,.footnote div.para {
+ padding-left:2em;
+}
+
+.footnote a:link,
+.footnote a:visited {
+ color:#00537c;
+}
+
+.footnote a:hover {
+}
+
+/**/
+div.chapter {
+ margin-top:3em;
+ page-break-inside: avoid;
+}
+
+div.preface {
+ page-break-inside: avoid;
+}
+
+div.section {
+ margin-top:1em;
+ page-break-inside: auto;
+}
+
+div.note .replaceable,
+div.important .replaceable,
+div.warning .replaceable,
+div.note .keycap,
+div.important .keycap,
+div.warning .keycap
+{
+}
+
+ul li p:last-child, ul li div.para:last-child {
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+/*document navigation*/
+.docnav a, .docnav strong {
+ border:none;
+ text-decoration:none;
+ font-weight:normal;
+}
+
+.docnav {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ position:relative;
+ width:100%;
+ padding-bottom:2em;
+ padding-top:1em;
+ border-top:1px dotted #ccc;
+}
+
+.docnav li {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ display:inline;
+ font-size:.8em;
+}
+
+.docnav li:before {
+ content:" ";
+}
+
+.docnav li.previous, .docnav li.next {
+ position:absolute;
+ top:1em;
+}
+
+.docnav li.up, .docnav li.home {
+ margin:0em 1.5em;
+}
+
+.docnav li.previous {
+ left:0px;
+ text-align:left;
+}
+
+.docnav li.next {
+ right:0px;
+ text-align:right;
+}
+
+.docnav li.previous strong, .docnav li.next strong {
+ height:22px;
+ display:block;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+.docnav li.next a strong {
+ background: url(../images/stock-go-forward.png) top right no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-right:28px;
+ font-size:1.2em;
+}
+
+.docnav li.previous a strong {
+ background: url(../images/stock-go-back.png) top left no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-left:28px;
+ padding-right:0.5em;
+ font-size:1.2em;
+}
+
+.docnav li.home a strong {
+ background: url(../images/stock-home.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav li.up a strong {
+ background: url(../images/stock-go-up.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav a:link, .docnav a:visited {
+ color:#666;
+}
+
+.docnav a:hover, .docnav a:focus, .docnav a:active {
+ color:black;
+}
+
+.docnav a {
+ max-width: 10em;
+ overflow:hidden;
+}
+
+.docnav a:link strong {
+ text-decoration:none;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+ul.docnav {
+ margin-bottom: 1em;
+}
+/* Reports */
+.reports ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.reports li{
+ margin:0em;
+ padding:0em;
+}
+
+.reports li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.reports dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.reports h2, .reports h3{
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.reports div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/*uniform*/
+body.results, body.reports {
+ max-width:57em ;
+ padding:0em;
+}
+
+/*Progress Bar*/
+div.progress {
+ display:block;
+ float:left;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ height:1em;
+}
+
+div.progress span {
+ height:1em;
+ float:left;
+}
+
+div.progress span.translated {
+ background:#6c3 url(../images/shine.png) top left repeat-x;
+}
+
+div.progress span.fuzzy {
+ background:#ff9f00 url(../images/shine.png) top left repeat-x;
+}
+
+
+/*Results*/
+
+.results ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.results li{
+ margin:0em;
+ padding:0em;
+}
+
+.results li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.results dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.results dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.results dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.results h2, .results h3 {
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.results div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/* Dirty EVIL Mozilla hack for round corners */
+pre {
+ -moz-border-radius:11px;
+ -webkit-border-radius:11px;
+ border-radius: 11px;
+ page-break-inside: avoid;
+}
+
+.example {
+ -moz-border-radius:0px;
+ -webkit-border-radius:0px;
+ border-radius: 0px;
+ page-break-inside: avoid;
+}
+
+.package, .citetitle {
+ font-style: italic;
+}
+
+.titlepage .edition {
+ color: #336699;
+ background-color: transparent;
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ font-weight: bold;
+ text-align: center;
+}
+
+span.remark {
+ background-color: #ff00ff;
+}
+
+.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+.foreignphrase {
+ font-style: inherit;
+}
+
+dt {
+ clear:both;
+}
+
+dt img {
+ border-style: none;
+ max-width: 112px;
+}
+
+dt object {
+ max-width: 112px;
+}
+
+dt .inlinemediaobject, dt object {
+ display: inline;
+ float: left;
+ margin-bottom: 1em;
+ padding-right: 1em;
+ width: 112px;
+}
+
+dl:after {
+ display: block;
+ clear: both;
+ content: "";
+}
+
+.toc dd {
+ padding-bottom: 0em;
+ margin-bottom: 1em;
+ padding-left: 1.3em;
+ margin-left: 0em;
+}
+
+div.toc > dl > dt {
+ padding-bottom: 0em;
+ margin-bottom: 0em;
+ margin-top: 1em;
+}
+
+
+.strikethrough {
+ text-decoration: line-through;
+}
+
+.underline {
+ text-decoration: underline;
+}
+
+.calloutlist img, .callout {
+ padding: 0em;
+ margin: 0em;
+ width: 12pt;
+ display: inline;
+ vertical-align: middle;
+}
+
+.stepalternatives {
+ list-style-image: none;
+ list-style-type: none;
+}
+
+
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/css/default.css b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/css/lang.css b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/css/overrides.css b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..057be29
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/css/overrides.css
@@ -0,0 +1,51 @@
+a:link {
+ color:#0066cc;
+}
+
+a:hover, a:active {
+ color:#003366;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+
+h1 {
+ color:#3c6eb4
+}
+
+.producttitle {
+ background: #3c6eb4 url(../images/h1-bg.png) top left repeat;
+}
+
+.section h1.title {
+ color:#3c6eb4;
+}
+
+
+h2,h3,h4,h5,h6 {
+ color:#3c6eb4;
+}
+
+table {
+ border:1px solid #3c6eb4;
+}
+
+table th {
+ background-color:#3c6eb4;
+}
+
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.revhistory table th {
+ color:#3c6eb4;
+}
+
+.titlepage .edition {
+ color: #3c6eb4;
+}
+
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/css/print.css b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/1.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..c21d7a3
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/1.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/1.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..a2b3903
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/1.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#000000;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 17.853468,22.008438 -2.564941,0 0,-7.022461 c -5e-6,-0.143873 -5e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224122,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08854,0.08302 -0.17432,0.157723 -0.257324,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/10.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..15b81da
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/10.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/10.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..af015ab
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/10.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/11.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..2fcc2dd
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/11.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/11.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..cb82b70
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/11.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/12.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..edebe20
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/12.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/12.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..3b6d822
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/12.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/13.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..ec48cef
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/13.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/13.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..226e461
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/13.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/14.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..33d5637
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/14.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/14.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..5aaa3a3
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/14.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/15.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..f1a4eb2
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/15.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/15.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..f51dd96
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/15.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2839"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2841"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/16.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..d38a155
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/16.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/16.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..cb7e2f5
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/16.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/17.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..d83e898
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/17.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/17.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..5d6f0ad
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/17.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/18.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..9e39de4
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/18.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/18.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..9ea672c
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/18.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/19.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..9eeedfb
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/19.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/19.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..80d1d09
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/19.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/2.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..ff9cc57
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/2.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/2.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..8e94260
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/2.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.89546,22.008438 -8.143066,0 0,-1.784668 2.855468,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979493,-1.0708 0.293289,-0.326492 0.545079,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.373529,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.17431,-0.666821 0.174316,-1.037598 -6e-6,-0.409496 -0.124517,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827313,0.522958 -1.270019,0.921386 l -1.394531,-1.651855 c 0.249022,-0.226877 0.509113,-0.442698 0.780273,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079102,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319824,-0.1494141 0.58105,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187012,0.6889648 0.326489,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.893727 0.265625,1.41
9433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/20.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..b28b4aa
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/20.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/20.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..409ac6e
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/20.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/21.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..eda952c
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/21.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/21.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..7bc03af
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/21.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/22.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..90b14b0
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/22.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/22.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..fe086f6
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/22.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/23.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..8b35a74
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/23.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/23.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..f17ec29
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/23.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/24.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/24.png
new file mode 100644
index 0000000..6041b02
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/24.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/24.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/24.svg
new file mode 100644
index 0000000..42a5333
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/24.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/25.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/25.png
new file mode 100644
index 0000000..ecb15e6
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/25.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/25.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/25.svg
new file mode 100644
index 0000000..a8d4672
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/25.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/26.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/26.png
new file mode 100644
index 0000000..4b2f560
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/26.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/26.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/26.svg
new file mode 100644
index 0000000..3cf00ec
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/26.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/27.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/27.png
new file mode 100644
index 0000000..ecf058e
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/27.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/27.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/27.svg
new file mode 100644
index 0000000..c8d6440
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/27.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/28.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/28.png
new file mode 100644
index 0000000..e64efb2
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/28.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/28.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/28.svg
new file mode 100644
index 0000000..5acce93
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/28.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/29.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/29.png
new file mode 100644
index 0000000..dbbca1b
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/29.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/29.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/29.svg
new file mode 100644
index 0000000..507dd44
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/29.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/3.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..4febe43
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/3.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/3.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..5e87e1f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/3.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.422316,12.587051 c -9e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.23243,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315437,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.392911,0.332031 -0.890957,0.592122 -1.494141,0.780273 -0.597661,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267255,-0.05534 -1.842773,-0.166016 -0.575523,-0.105143 -1.112306,-0.268392 -1.610352,-0.489746 l 0,-2.183105 c 0.249023,0.132815 0.511881,0.249025 0.788574,0.348632 0.276692,0.09961 0.553384,0.185387 0.830079,0.257325 0.27669,0.06641 0.547848,0.116212 0.813476,0.149414 0.271156,0.0332 0.525713,0.04981 0.763672,0.0498 0.475907,2e-6 0.871577,-0.04427 1.187012,-0.132812 0.315424,-
0.08854 0.567214,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320957,-0.351397 0.398437,-0.572754 0.083,-0.226885 0.124506,-0.473141 0.124512,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.265631,-0.376297 -0.498047,-0.514648 -0.226893,-0.143876 -0.525721,-0.254553 -0.896484,-0.332032 -0.370773,-0.07747 -0.827315,-0.116205 -1.369629,-0.116211 l -0.863281,0 0,-1.801269 0.846679,0 c 0.509111,7e-6 0.932451,-0.04426 1.27002,-0.132813 0.33756,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.43164,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.68897,-0.365224 -1.27002,-0.365234 -0.265629,10e-6 -0.514652,0.02768 -0.74707,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193688,0.07748 -0.373538,0.166026 -0.539551,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439941,0.282227 l -1.294922,-1.70
9961 c 0.232421,-0.171538 0.484211,-0.329253 0.755371,-0.473145 0.276691,-0.143868 0.575519,-0.26838 0.896484,-0.373535 0.320961,-0.1106647 0.666827,-0.1964393 1.037598,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492506,0.1272911 0.913079,0.3154421 1.261718,0.5644531 0.348626,0.243501 0.617017,0.545096 0.805176,0.904786 0.193677,0.354177 0.290519,0.760914 0.290528,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/30.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/30.png
new file mode 100644
index 0000000..f4ffb14
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/30.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/30.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/30.svg
new file mode 100644
index 0000000..434e663
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/30.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/31.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/31.png
new file mode 100644
index 0000000..0b29e87
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/31.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/31.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/31.svg
new file mode 100644
index 0000000..08c3f2d
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/31.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/32.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/32.png
new file mode 100644
index 0000000..a4740a3
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/32.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/32.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/32.svg
new file mode 100644
index 0000000..aa099c3
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/32.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/33.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/33.png
new file mode 100644
index 0000000..f23ccea
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/33.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/33.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/33.svg
new file mode 100644
index 0000000..fce979c
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/33.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/34.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/34.png
new file mode 100644
index 0000000..7e2ab31
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/34.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/34.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/34.svg
new file mode 100644
index 0000000..c67f8ec
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/34.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/35.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/35.png
new file mode 100644
index 0000000..02118e3
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/35.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/35.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/35.svg
new file mode 100644
index 0000000..da7780a
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/35.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/36.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/36.png
new file mode 100644
index 0000000..30f4fdf
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/36.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/36.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/36.svg
new file mode 100644
index 0000000..348549a
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/36.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/37.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/37.png
new file mode 100644
index 0000000..6174706
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/37.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/37.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/37.svg
new file mode 100644
index 0000000..7bc04d9
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/37.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/38.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/38.png
new file mode 100644
index 0000000..161661d
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/38.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/38.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/38.svg
new file mode 100644
index 0000000..ec2ad98
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/38.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/39.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/39.png
new file mode 100644
index 0000000..2d46b24
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/39.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/39.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/39.svg
new file mode 100644
index 0000000..664ffdd
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/39.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/4.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..9b9dd88
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/4.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/4.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..bc06c73
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/4.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 20.078077,19.493301 -1.460937,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460937,0 0,1.992187 m -3.959472,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09962,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.12175,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.025391,3.071289 2.75586,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/40.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/40.png
new file mode 100644
index 0000000..fe2a68f
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/40.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/40.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/40.svg
new file mode 100644
index 0000000..5a94d1b
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/40.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.440535,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.0136719,0 0,-1.784668 5.1547849,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.0253904,3.071289 2.7558594,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/5.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..f239fb6
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/5.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/5.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..82fb03d
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/5.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 16.035597,14.255508 c 0.520177,8e-6 1.004388,0.08025 1.452637,0.240723 0.448235,0.160489 0.838371,0.395678 1.17041,0.705566 0.332023,0.309903 0.592114,0.697272 0.780273,1.16211 0.188143,0.459315 0.282218,0.987797 0.282227,1.585449 -9e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.204761,0.520184 -0.506356,0.962892 -0.904785,1.328125 -0.398445,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261724,0.290528 -2.025391,0.290528 -0.304365,0 -0.60596,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863281,-0.124512 -0.271161,-0.04981 -0.531252,-0.116211 -0.780274,-0.199219 -0.24349,-0.08301 -0.464844,-0.17985 -0.664062,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672363,0.31543 0.254556,0.09408 0.517414,0.177086 0.788574,0.249024 0.276691,0.06641 0.553383,0.121746 0.830078,0.166015 0.27669,0.03874 0.539548,0.05811 0.788575,0.05811 0.741532,2e-6 1.305984,-0.152179 1.693359,-0.456543 0.387364,-0.309893 0.5810
49,-0.799639 0.581055,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751465,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320966,0.03874 -0.481445,0.06641 -0.154951,0.02768 -0.304365,0.05811 -0.448242,0.09131 -0.143883,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456542,-6.1840821 6.408204,0 0,2.1748051 -4.183594,0 -0.199219,2.382324 c 0.17708,-0.03873 0.381832,-0.07747 0.614258,-0.116211 0.237951,-0.03873 0.542313,-0.0581 0.913086,-0.05811"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/6.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..18866e6
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/6.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/6.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..e2f62af
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/6.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 11.702589,16.853653 c -10e-7,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.0664,-0.575514 0.179849,-1.126132 0.340332,-1.651856 0.166014,-0.531241 0.387368,-1.023753 0.664062,-1.477539 0.282225,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431638,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603186,-0.1936727 1.305984,-0.2905151 2.108399,-0.2905274 0.116204,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.138339,0.00555 0.276685,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251782,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210295,-0.04979 -0.434416,-0.08853 -0.672364,-0.116211 -0.232429,-0.03319 -0.467617,-0.04979 -0.705566,-0.0498 -0.747076,1e-5 -1.361334,0.09408 -1.842774,0.282226 -0.481449,0.182627 -0.863285,0.439951 -1.145507,0.771973 -0.28223,0.33204 -0.484216,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.215821,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243486,-0.384596 0.39843
7,-0.556153 0.160478,-0.177076 0.345862,-0.32649 0.556153,-0.448242 0.210282,-0.127271 0.44547,-0.22688 0.705566,-0.298828 0.26562,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419433,0.257324 0.420566,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.15494,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282226,1.768066 -0.182626,0.520184 -0.445484,0.962892 -0.788575,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643554,0.282227 -0.597661,0 -1.15658,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.973961,-0.542317 -1.361328,-0.979492 -0.381838,-0.437173 -0.683433,-0.987791 -0.904785,-1.651856 -0.215822,-0.669593 -0.323732,-1.460933 -0.323731,-2.374023 m 4.216797,3.270508 c 0.226883,2e-6 0.431635,-0.0415 0.614258,-0.124512 0.188145,-0.08854 0.348627,-0.218585 0.481445,-0.390137 0.13834,-0.17708 0.243483,-0.3
98434 0.31543,-0.664062 0.07747,-0.265622 0.116204,-0.581051 0.116211,-0.946289 -7e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243496,-0.343094 -0.617031,-0.514643 -1.120606,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.39014,0.229661 -0.53955,0.390137 -0.149418,0.160487 -0.265629,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.31543,0.755371 0.143876,0.221357 0.318193,0.401207 0.522949,0.539551 0.210282,0.138349 0.453772,0.207522 0.730469,0.20752"
+ id="path2846"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/7.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..52c3a18
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/7.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/7.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..a43460f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/7.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 12.789991,22.008438 4.316407,-9.960937 -5.578125,0 0,-2.1582035 8.367187,0 0,1.6103515 -4.424316,10.508789 -2.681153,0"
+ id="path2832"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/8.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..8a8cb21
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/8.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/8.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..2c82d3f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/8.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.761671,9.7149811 c 0.503576,1.23e-5 0.979487,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337558,0.243501 0.60595,0.547862 0.805176,0.913086 0.199211,0.365244 0.29882,0.794118 0.298828,1.286621 -8e-6,0.365243 -0.05535,0.697274 -0.166015,0.996094 -0.110686,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193693,0.237963 -0.423348,0.451017 -0.688965,0.639161 -0.265632,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.633619,0.362473 0.937988,0.572754 0.309888,0.210292 0.583814,0.448247 0.821777,0.713867 0.237948,0.260096 0.428866,0.55339 0.572754,0.879883 0.143872,0.326501 0.215812,0.691735 0.21582,1.095703 -8e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478686,0.758139 -0.838379,1.045898 -0.359707,0.287761 -0.791348,0.509115 -1.294921,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651856,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.9379
9,-0.362467 -1.286621,-0.639161 -0.348634,-0.276691 -0.614259,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265626,-0.857744 -0.265625,-1.361328 -10e-7,-0.415035 0.06087,-0.78857 0.182617,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498047,-0.896485 0.210285,-0.265619 0.456541,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271162,-0.171543 -0.525719,-0.356927 -0.763672,-0.556152 -0.237958,-0.204746 -0.445477,-0.428866 -0.622559,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -10e-7,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478677,-0.669585 0.821778,-0.913086 0.343096,-0.249012 0.738766,-0.434396 1.187011,-0.5561527 0.448239,-0.1217326 0.918616,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.107911,0.614258 0.07194,0.18262 0.17708,0.340334 0.315429,0.473145 0.143877,0.132814 0.32
096,0.237957 0.53125,0.315429 0.210283,0.07194 0.453772,0.107912 0.730469,0.10791 0.581049,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.43164,-1.087402 -6e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218593,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.320969,-0.307125 -0.514648,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 15.662062,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664063,0.398438 -0.199222,0.138351 -0.370772,0.293299 -0.514648,0.464844 -0.13835,0.16602 -0.24626,0.348637 -0.323731,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.701661,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514649,0.08301 -0.154952,0.05535 -0.290531,0.13559 -0.406738,0.240723 -0.110681,0.105153 -0.199223,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.31543
8 0.282226,0.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160478,0.09962 0.32926,0.199226 0.506348,0.298828 0.171545,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154943,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.12174,-0.138338 0.218582,-0.293286 0.290528,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.157721,-0.284984 -0.273926,-0.390137 -0.116217,-0.105133 -0.254563,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/9.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..0ae412f
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/9.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/9.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..b0f04c4
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/9.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.829054,15.052383 c -9e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340333,1.651856 -0.160489,0.525719 -0.381843,1.018232 -0.664062,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426113,0.332032 -0.940761,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.30046,0.282227 -2.108399,0.282227 -0.116214,0 -0.243492,-0.0028 -0.381836,-0.0083 -0.138348,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273927,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237954,0.02767 0.478676,0.04151 0.722168,0.0415 0.747067,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.481441,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.282221,-0.337562 0.481439,-0.738766 0.597657,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.107911,0 c -0.110683,0.199225 -0.243495,0.384609 -0.398437,0.556153 -0.
154954,0.171554 -0.337571,0.320968 -0.547852,0.448242 -0.210291,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.265629,0.07194 -0.56169,0.107914 -0.888183,0.10791 -0.52572,4e-6 -0.998864,-0.08577 -1.419434,-0.257324 -0.420575,-0.171545 -0.777508,-0.420568 -1.070801,-0.74707 -0.287761,-0.326492 -0.509115,-0.727696 -0.664062,-1.203614 -0.154949,-0.475904 -0.232423,-1.020988 -0.232422,-1.635253 -10e-7,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453774,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758135,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043127,-0.2905151 1.651855,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520176,0.210298 0.971184,0.534028 1.353027,0.971192 0.381829,0.437185 0.683423,0.990569 0.904786,1.660156 0.221345,0.669605 0.332022,1.458178 0.332031,2.365722 m -4.216797,-3.262207 c -0.226892,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188154,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132815,0.17155
9 -0.237959,0.392913 -0.315429,0.664062 -0.07194,0.265634 -0.107914,0.581063 -0.107911,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373536,1.394532 0.249019,0.343105 0.625321,0.514654 1.128906,0.514648 0.254552,6e-6 0.486974,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.53955,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124506,-0.401197 0.124512,-0.605958 -6e-6,-0.282218 -0.03598,-0.561677 -0.10791,-0.838378 -0.06641,-0.282218 -0.171556,-0.534008 -0.31543,-0.755372 -0.138352,-0.226878 -0.312668,-0.409495 -0.522949,-0.547851 -0.204758,-0.138336 -0.44548,-0.207509 -0.722168,-0.20752"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/bkgrnd_greydots.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/bkgrnd_greydots.png
new file mode 100644
index 0000000..2333a6d
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/bkgrnd_greydots.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/bullet_arrowblue.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/bullet_arrowblue.png
new file mode 100644
index 0000000..c235534
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/bullet_arrowblue.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/documentation.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/documentation.png
new file mode 100644
index 0000000..79d0a80
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/documentation.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/dot.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/dot.png
new file mode 100644
index 0000000..36a6859
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/dot.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/dot2.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/dot2.png
new file mode 100644
index 0000000..40aff92
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/dot2.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/green.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/green.png
new file mode 100644
index 0000000..ebb3c24
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/green.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/h1-bg.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/h1-bg.png
new file mode 100644
index 0000000..a2aad24
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/h1-bg.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/image_left.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/image_left.png
new file mode 100644
index 0000000..e8fe7a4
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/image_left.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/image_right.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/image_right.png
new file mode 100644
index 0000000..5b67443
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/image_right.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/important.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/important.png
new file mode 100644
index 0000000..f7594a3
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/important.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/important.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..2d33045
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/important.svg
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="important.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/important.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2611">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="681"
+ inkscape:window-width="738"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2613" />
+ </defs>
+ <g
+ transform="matrix(0.4626799,0,0,0.4626799,-5.2934127,-3.3160376)"
+ id="g5485">
+ <path
+ d="M 29.97756,91.885882 L 55.586992,80.409826 L 81.231619,91.807015 L 78.230933,63.90468 L 96.995009,43.037218 L 69.531053,37.26873 L 55.483259,12.974592 L 41.510292,37.311767 L 14.064204,43.164717 L 32.892392,63.97442 L 29.97756,91.885882 z"
+ id="path6799"
+ style="fill:#f3de82;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.536215,56.538729 L 55.48324,12.974601 L 41.51028,37.311813 L 55.536215,56.538729 z"
+ id="path6824"
+ style="opacity:0.91005291;fill:#f9f2cb;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 78.241135,63.937979 L 96.976198,43.044318 L 55.57947,56.614318 z"
+ id="use6833"
+ style="opacity:1;fill:#d0bc64;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 55.667994,80.684281 L 81.379011,91.931065 L 55.523838,56.869126 z"
+ id="use6835"
+ style="opacity:1;fill:#e0c656;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 13.877363,43.200977 L 32.640089,64.069652 L 55.283346,56.742618 z"
+ id="use6831"
+ style="opacity:1;fill:#d1ba59;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 55.32792,80.684281 L 29.616903,91.931065 L 55.472076,56.869126 z"
+ id="use6837"
+ style="opacity:1;fill:#d2b951;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 96.976198,43.044318 L 69.504294,37.314027 L 55.57947,56.614318 z"
+ id="path7073"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 81.379011,91.931065 L 78.214821,64.046881 L 55.523838,56.869126 z"
+ id="path7075"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 41.341708,37.434209 L 13.877363,43.200977 L 55.283346,56.742618 z"
+ id="path7077"
+ style="opacity:1;fill:#f6e59d;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 29.616903,91.931065 L 32.781093,64.046881 L 55.472076,56.869126 z"
+ id="path7079"
+ style="opacity:1;fill:#f3df8b;fill-opacity:1;enable-background:new" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/logo.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/logo.png
new file mode 100644
index 0000000..66a3104
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/logo.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/note.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/note.png
new file mode 100644
index 0000000..d6c4518
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/note.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/note.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..70e43b6
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/note.svg
@@ -0,0 +1,111 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="note.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/note.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata16">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="1024"
+ inkscape:window-width="1205"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="22.217181"
+ inkscape:cy="20"
+ inkscape:window-x="334"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective18" />
+ </defs>
+ <g
+ transform="matrix(0.468275,0,0,0.468275,-5.7626904,-7.4142703)"
+ id="layer1">
+ <g
+ transform="matrix(0.115136,0,0,0.115136,9.7283,21.77356)"
+ id="g8014"
+ style="enable-background:new">
+ <g
+ id="g8518"
+ style="opacity:1">
+ <path
+ d="M -2512.4524,56.33197 L 3090.4719,56.33197 L 3090.4719,4607.3813 L -2512.4524,4607.3813 L -2512.4524,56.33197 z"
+ transform="matrix(0.1104659,-2.3734892e-2,2.2163258e-2,0.1031513,308.46782,74.820675)"
+ id="rect8018"
+ style="fill:#ffe680;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ <g
+ transform="matrix(0.5141653,-7.1944682e-2,7.1944682e-2,0.5141653,146.04015,-82.639785)"
+ id="g8020">
+ <path
+ d="M 511.14114,441.25315 C 527.3248,533.52772 464.31248,622.82928 370.39916,640.71378 C 276.48584,658.59828 187.23462,598.29322 171.05095,506.01865 C 154.86728,413.74408 217.8796,324.44253 311.79292,306.55803 C 405.70624,288.67353 494.95747,348.97858 511.14114,441.25315 z"
+ id="path8022"
+ style="opacity:1;fill:#e0c96f;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(1.2585415,-0.2300055,0.2168789,1.1867072,-248.76141,68.254424)"
+ id="path8024"
+ style="opacity:1;fill:#c00000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 358.5625,281.15625 C 348.09597,281.05155 337.43773,281.94729 326.71875,283.90625 C 240.96686,299.57789 183.37901,377.92385 198.15625,458.78125 C 209.70749,521.98673 262.12957,567.92122 325.40625,577.5625 L 357.25,433.6875 L 509.34375,405.875 C 509.14405,404.58166 509.0804,403.29487 508.84375,402 C 495.91366,331.24978 431.82821,281.88918 358.5625,281.15625 z"
+ id="path8026"
+ style="opacity:1;fill:#b60000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 294.2107,361.9442 L 282.79367,370.38482 L 261.73414,386.13346 C 253.13706,404.40842 254.3359,423.7989 259.7176,444.39774 C 273.6797,497.83861 313.42636,523.96124 369.50989,517.58957 C 398.21848,514.32797 424.51832,504.67345 440.64696,484.15958 L 469.89512,447.48298 L 294.2107,361.9442 z"
+ id="path8028"
+ style="fill:#750000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.09999999;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-78.013985,79.234385)"
+ id="path8030"
+ style="opacity:1;fill:#d40000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-69.306684,71.273294)"
+ id="path8032"
+ style="opacity:1;fill:#e11212;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/red.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/red.png
new file mode 100644
index 0000000..d32d5e2
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/red.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/shade.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/shade.png
new file mode 100644
index 0000000..a73afdf
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/shade.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/shine.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/shine.png
new file mode 100644
index 0000000..a18f7c4
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/shine.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/stock-go-back.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/stock-go-back.png
new file mode 100644
index 0000000..d320f26
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/stock-go-back.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/stock-go-forward.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/stock-go-forward.png
new file mode 100644
index 0000000..1ee5a29
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/stock-go-forward.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/stock-go-up.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/stock-go-up.png
new file mode 100644
index 0000000..1cd7332
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/stock-go-up.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/stock-home.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/stock-home.png
new file mode 100644
index 0000000..122536d
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/stock-home.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/title_logo.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/title_logo.png
new file mode 100644
index 0000000..d5182b4
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/title_logo.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/title_logo.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/title_logo.svg
new file mode 100644
index 0000000..e8fd52b
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/title_logo.svg
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="220"
+ height="70"
+ id="svg6180">
+ <defs
+ id="defs6182" />
+ <g
+ transform="translate(-266.55899,-345.34488)"
+ id="layer1">
+ <path
+ d="m 316.7736,397.581 c 0,0 0,0 -20.53889,0 0.3327,4.45245 3.92157,7.77609 8.70715,7.77609 3.38983,0 6.31456,-1.39616 8.64094,-3.65507 0.46553,-0.46679 0.99726,-0.59962 1.59519,-0.59962 0.79781,0 1.59561,0.39932 2.12692,1.06388 0.3327,0.46553 0.53216,0.99726 0.53216,1.52857 0,0.73118 -0.3327,1.52857 -0.93106,2.12734 -2.7919,2.99052 -7.51086,4.98503 -12.16403,4.98503 -8.44149,0 -15.22074,-6.77967 -15.22074,-15.22158 0,-8.44149 6.58022,-15.22074 15.02171,-15.22074 8.37529,0 14.62323,6.51317 14.62323,15.08749 0,1.26418 -1.12924,2.12861 -2.39258,2.12861 z m -12.23065,-11.76512 c -4.45329,0 -7.51085,2.92473 -8.17499,7.17731 10.03626,0 16.35083,0 16.35083,0 -0.59836,-4.05355 -3.78874,-7.17731 -8.17584,-7.17731 z"
+ id="path11"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 375.46344,410.80807 c -8.44106,0 -15.22074,-6.77968 -15.22074,-15.22159 0,-8.44149 6.77968,-15.22074 15.22074,-15.22074 8.44234,0 15.22159,6.77925 15.22159,15.22074 -4.2e-4,8.44149 -6.77968,15.22159 -15.22159,15.22159 z m 0,-24.65992 c -5.31688,0 -8.77377,4.25427 -8.77377,9.43833 0,5.18364 3.45689,9.43833 8.77377,9.43833 5.31731,0 8.77504,-4.25469 8.77504,-9.43833 -4.2e-4,-5.18406 -3.45773,-9.43833 -8.77504,-9.43833 z"
+ id="path13"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 412.66183,380.36574 c -4.45963,0 -7.40966,1.319 -10.01391,4.62956 l -0.24036,-1.53995 0,0 c -0.20198,-1.60743 -1.57326,-2.84926 -3.23382,-2.84926 -1.80139,0 -3.26206,1.459 -3.26206,3.26081 0,0.003 0,0.005 0,0.008 l 0,0 0,0.003 0,0 0,23.40712 c 0,1.79464 1.46194,3.25743 3.257,3.25743 1.79465,0 3.25744,-1.46279 3.25744,-3.25743 l 0,-12.56209 c 0,-5.71621 4.98502,-8.57432 10.23613,-8.57432 1.59519,0 2.85726,-1.32953 2.85726,-2.92515 0,-1.59561 -1.26207,-2.85726 -2.85768,-2.85726 z"
+ id="path15"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 447.02614,395.58648 c 0.0666,-8.17541 -5.78326,-15.22074 -15.222,-15.22074 -8.44192,0 -15.28779,6.77925 -15.28779,15.22074 0,8.44191 6.64684,15.22159 14.68985,15.22159 4.01434,0 7.62682,-2.06621 9.23846,-4.22518 l 0.79359,2.01434 0,0 c 0.42589,1.13177 1.5176,1.93717 2.7978,1.93717 1.65001,0 2.98756,-1.33671 2.99009,-2.98545 l 0,0 0,-7.80687 0,0 0,-4.1556 z m -15.222,9.43833 c -5.31773,0 -8.77419,-4.25469 -8.77419,-9.43833 0,-5.18406 3.45604,-9.43833 8.77419,-9.43833 5.3173,0 8.77419,4.25427 8.77419,9.43833 0,5.18364 -3.45689,9.43833 -8.77419,9.43833 z"
+ id="path17"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 355.01479,368.3337 c 0,-1.7938 -1.46194,-3.18997 -3.25659,-3.18997 -1.79422,0 -3.25743,1.39659 -3.25743,3.18997 l 0,17.1499 c -1.66097,-3.05756 -5.25026,-5.11786 -9.50495,-5.11786 -8.64052,0 -14.42336,6.51318 -14.42336,15.22074 0,8.70757 5.98229,15.22159 14.42336,15.22159 3.76555,0 7.03057,-1.55429 8.98587,-4.25554 l 0.72317,1.83428 c 0.44782,1.25912 1.64917,2.16024 3.06051,2.16024 1.78621,0 3.24984,-1.45435 3.24984,-3.24815 0,-0.005 0,-0.009 0,-0.0139 l 0,0 0,-38.95128 -4.2e-4,0 z m -15.22116,36.69111 c -5.31731,0 -8.70715,-4.25469 -8.70715,-9.43833 0,-5.18406 3.38984,-9.43833 8.70715,-9.43833 5.31773,0 8.70714,4.0544 8.70714,9.43833 0,5.38309 -3.38941,9.43833 -8.70714,9.43833 z"
+ id="path19"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 287.21553,365.34023 c -0.59414,-0.0877 -1.19966,-0.13198 -1.80097,-0.13198 -6.73118,0 -12.20746,5.4767 -12.20746,12.20788 l 0,3.8132 -3.98903,0 c -1.46237,0 -2.65908,1.19671 -2.65908,2.65781 0,1.46321 1.19671,2.93738 2.65908,2.93738 l 3.98819,0 0,20.46004 c 0,1.79464 1.46236,3.25743 3.25658,3.25743 1.79507,0 3.25744,-1.46279 3.25744,-3.25743 l 0,-20.46004 4.40986,0 c 1.46194,0 2.65823,-1.47417 2.65823,-2.93738 0,-1.46152 -1.19629,-2.65823 -2.65823,-2.65823 l -4.40733,0 0,-3.8132 c 0,-3.13852 2.55323,-6.11469 5.69175,-6.11469 0.28294,0 0.56757,0.0211 0.84672,0.062 1.78031,0.26355 3.4358,-0.54269 3.70019,-2.32342 0.2627,-1.77904 -0.96606,-3.43538 -2.74594,-3.69935 z"
+ id="path21"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 482.01243,363.57426 c 0,-10.06788 -8.16108,-18.22938 -18.22897,-18.22938 -10.06282,0 -18.22179,8.15475 -18.22854,18.21631 l -4.2e-4,-4.2e-4 0,14.1071 4.2e-4,4.2e-4 c 0.005,2.28463 1.85832,4.13409 4.14463,4.13409 0.007,0 0.0127,-8.4e-4 0.0194,-8.4e-4 l 0.001,8.4e-4 14.07083,0 0,0 c 10.06409,-0.004 18.22138,-8.16276 18.22138,-18.22812 z"
+ id="path25"
+ style="fill:#294172" />
+ <path
+ d="m 469.13577,349.66577 c -4.72528,0 -8.55576,3.83049 -8.55576,8.55577 0,0.002 0,0.004 0,0.006 l 0,4.52836 -4.51444,0 c -8.5e-4,0 -8.5e-4,0 -0.001,0 -4.72528,0 -8.55576,3.81193 -8.55576,8.53678 0,4.72528 3.83048,8.55577 8.55576,8.55577 4.72486,0 8.55534,-3.83049 8.55534,-8.55577 0,-0.002 0,-0.004 0,-0.006 l 0,-4.54733 4.51444,0 c 8.5e-4,0 0.001,0 0.002,0 4.72486,0 8.55534,-3.79296 8.55534,-8.51781 0,-4.72528 -3.83048,-8.55577 -8.55534,-8.55577 z m -8.55576,21.63483 c -0.004,2.48998 -2.02446,4.50811 -4.51571,4.50811 -2.49378,0 -4.53426,-2.02193 -4.53426,-4.5157 0,-2.49421 2.04048,-4.55366 4.53426,-4.55366 0.002,0 0.004,4.2e-4 0.006,4.2e-4 l 3.86971,0 c 0.001,0 0.002,-4.2e-4 0.003,-4.2e-4 0.35209,0 0.63799,0.28505 0.63799,0.63715 0,4.2e-4 -4.2e-4,8.4e-4 -4.2e-4,0.001 l 0,3.92284 -4.2e-4,0 z m 8.55534,-8.5448 c -0.001,0 -0.003,0 -0.004,0 l -3.87223,0 c -8.4e-4,0 -0.002,0 -0.002,0 -0.35252,0 -0.63757,-0.28506 -0.63757,-0.63758 l 0,-4.2e-4 0,-3.90343 c 0.004,-2.49083 2.02
446,-4.50854 4.51571,-4.50854 2.49378,0 4.53468,2.02193 4.53468,4.51613 4.2e-4,2.49336 -2.04048,4.53384 -4.53426,4.53384 z"
+ id="path29"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 460.58001,362.7558 0,-4.52836 c 0,-0.002 0,-0.004 0,-0.006 0,-4.72528 3.83048,-8.55577 8.55576,-8.55577 0.71685,0 1.22623,0.0805 1.88952,0.25469 0.96774,0.25385 1.75796,1.04618 1.75838,1.96922 4.2e-4,1.11575 -0.80919,1.92621 -2.0194,1.92621 -0.57642,0 -0.78473,-0.11048 -1.62892,-0.11048 -2.49125,0 -4.51149,2.01771 -4.51571,4.50854 l 0,3.90385 0,4.2e-4 c 0,0.35252 0.28505,0.63758 0.63757,0.63758 4.3e-4,0 0.001,0 0.002,0 l 2.96521,0 c 1.10521,0 1.99747,0.88467 1.99832,1.99283 0,1.10816 -0.89353,1.99114 -1.99832,1.99114 l -3.60489,0 0,4.54733 c 0,0.002 0,0.004 0,0.006 0,4.72485 -3.83048,8.55534 -8.55534,8.55534 -0.71684,0 -1.22623,-0.0805 -1.88952,-0.25469 -0.96774,-0.25343 -1.75838,-1.04618 -1.7588,-1.9688 0,-1.11575 0.80919,-1.92663 2.01982,-1.92663 0.576,0 0.78473,0.11048 1.6285,0.11048 2.49125,0 4.51191,-2.01771 4.51613,-4.50811 0,0 0,-3.92368 0,-3.9241 0,-0.35168 -0.2859,-0.63673 -0.63799,-0.63673 -4.3e-4,0 -8.5e-4,0 -0.002,0 l -2.96521,-4.2e-4 c -1.10521,0 -1.
99831,-0.88214 -1.99831,-1.9903 -4.3e-4,-1.11533 0.90238,-1.99367 2.01939,-1.99367 l 3.58339,0 0,0 z"
+ id="path31"
+ style="fill:#ffffff" />
+ <path
+ d="m 477.41661,378.55292 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0 0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496 0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279 0,2.9226 -0.43694,0 0,-3.32833"
+ id="text6223"
+ style="fill:#294172;enable-background:new" />
+ </g>
+ <path
+ d="m 181.98344,61.675273 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0 0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496 0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279 0,2.9226 -0.43694,0 0,-3.32833"
+ id="path2391"
+ style="fill:#294172;enable-background:new" />
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/warning.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/warning.png
new file mode 100644
index 0000000..ce09951
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/warning.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/warning.svg b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..5f2612c
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/warning.svg
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="warning.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/warning.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2482">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="910"
+ inkscape:window-width="1284"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2484" />
+ </defs>
+ <g
+ transform="matrix(0.4536635,0,0,0.4536635,-5.1836431,-4.6889387)"
+ id="layer1">
+ <g
+ transform="translate(2745.6887,-1555.5977)"
+ id="g8304"
+ style="enable-background:new">
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.8233528,8.9983906e-3,-8.9983906e-3,0.8233528,-1398.5561,740.7914)"
+ id="path8034"
+ style="opacity:1;fill:#efd259;fill-opacity:1;stroke:#efd259;stroke-opacity:1" />
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.6467652,7.0684723e-3,-7.0684723e-3,0.6467652,-1675.7492,927.16391)"
+ id="path8036"
+ style="opacity:1;fill:#a42324;fill-opacity:1;stroke:#a42324;stroke-opacity:1" />
+ <path
+ d="M -2686.7886,1597.753 C -2686.627,1596.5292 -2686.5462,1595.6987 -2686.5462,1595.218 C -2686.5462,1593.1637 -2688.0814,1592.0711 -2690.9899,1592.0711 C -2693.8985,1592.0711 -2695.4336,1593.12 -2695.4336,1595.218 C -2695.4336,1595.961 -2695.3528,1596.7914 -2695.1912,1597.753 L -2692.929,1614.4491 L -2689.0508,1614.4491 L -2686.7886,1597.753"
+ id="path8038"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ <path
+ d="M -2690.9899,1617.8197 C -2693.6124,1617.8197 -2695.8118,1619.9346 -2695.8118,1622.6416 C -2695.8118,1625.3486 -2693.6124,1627.4635 -2690.9899,1627.4635 C -2688.2829,1627.4635 -2686.168,1625.264 -2686.168,1622.6416 C -2686.168,1619.9346 -2688.2829,1617.8197 -2690.9899,1617.8197"
+ id="path8040"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/watermark-draft.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/watermark-draft.png
new file mode 100644
index 0000000..0ead5af
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/watermark-draft.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/yellow.png b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/yellow.png
new file mode 100644
index 0000000..223865d
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/Common_Content/images/yellow.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/app-Revision_History.html b/public_html/en-US/Fedora/21/html/Networking_Guide/app-Revision_History.html
new file mode 100644
index 0000000..eb29613
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/app-Revision_History.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix A. Revision History</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="index.html" title="Networking Guide" /><link rel="prev" href="sec-bind-additional-resources.html" title="10.2.8. Additional Resources" /><link rel="next" href="ix01.html" title="Index" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-bind-additional-resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ix01.html"><strong>Next</str
ong></a></li></ul><div xml:lang="en-US" class="appendix" id="app-Revision_History" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
+ <div class="revhistory"><table summary="Revision History"><tr><th align="left" valign="top" colspan="3"><strong>Revision History</strong></th></tr><tr><td align="left">Revision 2-0</td><td align="left">Tues Jan 6 2015</td><td align="left"><span class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td> Update for Fedora 21. </td></tr></table>
+
+ </td></tr><tr><td align="left">Revision 1-1.2</td><td align="left">Mon Jan 5 2015</td><td align="left"><span class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td> General update and corrections for Fedora 20. </td></tr></table>
+
+ </td></tr><tr><td align="left">Revision 1-1</td><td align="left">Fri Aug 1 2014</td><td align="left"><span class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td> First version of the Fedora Networking Guide. </td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-bind-additional-resources.html"><strong>Prev</strong>10.2.8. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ix01.html"><strong>Next</strong>Index</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_802_1Q_VLAN_Tagging.html b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_802_1Q_VLAN_Tagging.html
new file mode 100644
index 0000000..64a8ae9
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_802_1Q_VLAN_Tagging.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 7. Configure 802.1Q VLAN tagging</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="part-Networking.html" title="Part I. Networking" /><link rel="prev" href="sec-Network_Bridging-additional_resources.html" title="6.4. Additional Resources" /><link rel="next" href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html" title="7.2. Configure 802.1Q VLAN Tagging Using a GUI" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Network_Bridging-additio
nal_resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-Configure_802_1Q_VLAN_Tagging" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 7. Configure 802.1Q VLAN tagging</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Configure_802_1Q_VLAN_Tagging.html#sec-Selecting_VLAN_Interface_Configuration_Methods">7.1. Selecting VLAN Interface Configuration Methods</a></span></dt><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html">7.2. Configure 802.1Q VLAN Tagging Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html#sec-Establishing_a_VLAN_Connection">7.2.1. Establishing a VLAN Connection</a></span></dt></dl></dd><dt><span class="section"><a href="sec-C
onfigure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html">7.3. Configure 802.1Q VLAN Tagging Using the Command Line</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html#sec-Setting_Up_802.1Q_VLAN_Tagging_Using_ifcfg_Files">7.3.1. Setting Up 802.1Q VLAN Tagging Using ifcfg Files</a></span></dt><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_ip_Commands.html">7.3.2. Configure 802.1Q VLAN Tagging Using ip Commands</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli.html">7.4. Configure 802.1Q VLAN Tagging Using the Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging-additional_resources.html">7.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging-additional_resources.html#sec-Configure_802_1Q_VLAN_T
agging-docs-inst">7.5.1. Installed Documentation</a></span></dt></dl></dd></dl></div><div class="para">
+ To create a VLAN, an interface is created on another interface referred to as the <em class="firstterm">parent interface</em>. The VLAN interface will tag packets with the VLAN ID as they pass through the interface, and returning packets will be untagged. VLAN interface can be configured similarly to any other interface. The parent interface need not be an Ethernet interface. An 802.1Q VLAN tagging interface can be created on bridge, bond, and team interfaces, however there are some things to note:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ In the case of VLANs over bonds, it is important that the bond has slaves and that they are <span class="quote">“<span class="quote">up</span>”</span> before bringing up the VLAN interface. At the time of writing, adding a VLAN interface to a bond without slaves does not work.
+ </div></li><li class="listitem"><div class="para">
+ A VLAN slave cannot be configured on a bond with the <code class="option">fail_over_mac=follow</code> option, because the VLAN virtual device cannot change its MAC address to match the parent's new MAC address. In such a case, traffic would still be sent with the now incorrect source MAC address.
+ </div></li><li class="listitem"><div class="para">
+ Sending VLAN tagged packets through a network switch requires configuration of the switch. Refer to the documentation for the switch. For example, for Cisco switches the port must be assigned to one VLAN or configured to be a trunk port to accept tagged packets for multiple VLANs. Untagged packets can also be processed by a trunk port and processed as belonging to the <em class="firstterm">native VLAN</em>, however this is a security risk and may have been disabled, or by default not enabled, depending on the make of the switch.
+ </div></li><li class="listitem"><div class="para">
+ Some older network interface cards, loopback interfaces, Wimax cards, and some InfiniBand devices, are said to be <em class="firstterm">VLAN challenged</em>, meaning they cannot support VLANs. This is usually because the devices cannot cope with VLAN headers and the larger MTU size associated with tagged packets.
+ </div></li></ul></div><div class="section" id="sec-Selecting_VLAN_Interface_Configuration_Methods"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.1. Selecting VLAN Interface Configuration Methods</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>To configure a network using graphical user interface tools</strong></span>, proceed to <a class="xref" href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html">Section 7.2, “Configure 802.1Q VLAN Tagging Using a GUI”</a>
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>To configure a VLAN interface using</strong></span> <span class="application"><strong>NetworkManager</strong></span>'s command-line tool, <span class="application"><strong>nmcli</strong></span>, proceed to <a class="xref" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli.html">Section 7.4, “Configure 802.1Q VLAN Tagging Using the Command Line Tool, nmcli”</a>
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>To configure a network interface manually</strong></span>, see <a class="xref" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html">Section 7.3, “Configure 802.1Q VLAN Tagging Using the Command Line”</a>.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Network_Bridging-additional_resources.html"><strong>Prev</strong>6.4. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html"><strong>Next</strong>7.2. Configure 802.1Q VLAN Tagging Using a GUI</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Host_Names.html b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Host_Names.html
new file mode 100644
index 0000000..7561546
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Host_Names.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 3. Configure Host Names</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="part-Networking.html" title="Part I. Networking" /><link rel="prev" href="sec-Configure_Networking_Online_Documentation.html" title="2.5.2. Online Documentation" /><link rel="next" href="sec_Configuring_Host_Names_Using_hostnamectl.html" title="3.2. Configuring Host Names Using hostnamectl" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_Networking
_Online_Documentation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec_Configuring_Host_Names_Using_hostnamectl.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-Configure_Host_Names" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 3. Configure Host Names</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Configure_Host_Names.html#sec_Understanding_Host_Names">3.1. Understanding Host Names</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Host_Names.html#sec-Recommended_Naming_Practices">3.1.1. Recommended Naming Practices</a></span></dt></dl></dd><dt><span class="section"><a href="sec_Configuring_Host_Names_Using_hostnamectl.html">3.2. Configuring Host Names Using hostnamectl</a></span></dt><dd><dl><dt><span class="section"><a href="sec_Configuring_Host_Names_Using_hostnamectl.html#sec_View_All_the_Host_Names">3.2.1. Vie
w All the Host Names</a></span></dt><dt><span class="section"><a href="sec_Set_All_the_Host_Names.html">3.2.2. Set All the Host Names</a></span></dt><dt><span class="section"><a href="sec_Set_a_Particular_Host_Name.html">3.2.3. Set a Particular Host Name</a></span></dt><dt><span class="section"><a href="sec_Clear_a_Particular_Host_Name.html">3.2.4. Clear a Particular Host Name</a></span></dt><dt><span class="section"><a href="sec_Changing_Host_Names_Remotely.html">3.2.5. Changing Host Names Remotely</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Host_Names_Using_nmcli.html">3.3. Configuring Host Names Using nmcli</a></span></dt><dt><span class="section"><a href="sec-additional_resources.html">3.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-additional_resources.html#sec-hostnamectl-docs-inst">3.4.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-hostnamectl-Online_Documentation
.html">3.4.2. Online Documentation</a></span></dt></dl></dd></dl></div><div class="section" id="sec_Understanding_Host_Names"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.1. Understanding Host Names</h2></div></div></div><div class="para">
+ There are three classes of <code class="systemitem">hostname</code>: static, pretty, and transient.
+ </div><div class="para">
+ The <span class="quote">“<span class="quote">static</span>”</span> host name is the traditional <code class="systemitem">hostname</code>, which can be chosen by the user, and is stored in the <code class="filename">/etc/hostname</code> file. The <span class="quote">“<span class="quote">transient</span>”</span> <code class="systemitem">hostname</code> is a dynamic host name maintained by the kernel. It is initialized to the static host name by default, whose value defaults to <span class="quote">“<span class="quote">localhost</span>”</span>. It can be changed by <code class="systemitem">DHCP</code> or <code class="systemitem">mDNS</code> at runtime. The <span class="quote">“<span class="quote">pretty</span>”</span> <code class="systemitem">hostname</code> is a free-form UTF8 host name for presentation to the user.
+ <div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ A host name can be a free-form string up to 64 characters in length. However, Red Hat recommends that both static and transient names match the <em class="firstterm">fully-qualified domain name</em> (<acronym class="acronym">FQDN</acronym>) used for the machine in <code class="systemitem">DNS</code>, such as <code class="systemitem">host.example.com</code>. It is also recommended that the static and transient names consists only of 7 bit ASCII lower-case characters, no spaces or dots, and limits itself to the format allowed for <code class="systemitem">DNS</code> domain name labels, even though this is not a strict requirement. Older specifications do not permit the underscore, and so their use is not recommended.
+ </div><div class="para">
+ The <span class="application"><strong>hostnamectl</strong></span> tool will enforce the following: Static and transient host names to consist of <code class="literal">a-z</code>, <code class="literal">A-Z</code>, <code class="literal">0-9</code>, <span class="quote">“<span class="quote"><code class="literal">-</code></span>”</span>, <span class="quote">“<span class="quote"><code class="literal">_</code></span>”</span> and <span class="quote">“<span class="quote"><code class="literal">.</code></span>”</span> only, to not begin or end in a dot, and to not have two dots immediately following each other. The size limit of 64 characters is enforced.
+ </div></div></div>
+
+ </div><div class="section" id="sec-Recommended_Naming_Practices"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.1.1. Recommended Naming Practices</h3></div></div></div><div class="para">
+ The Internet Corporation for Assigned Names and Numbers (ICANN) sometimes adds previously unregistered Top-Level Domains (such as <code class="systemitem">.yourcompany</code>) to the public register. Therefore, Red Hat strongly recommends that you do not use a domain name that is not delegated to you, even on a private network, as this can result in a domain name that resolves differently depending on network configuration. As a result, network resources can become unavailable. Using domain names that are not delegated to you also makes DNSSEC more difficult to deploy and maintain, as domain name collisions require manual configuration to enable DNSSEC validation. See the <a href="http://www.icann.org/en/help/name-collision/faqs">ICANN FAQ on domain name collision</a> for more information on this issue.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_Networking_Online_Documentation.html"><strong>Prev</strong>2.5.2. Online Documentation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec_Configuring_Host_Names_Using_hostnamectl.html"><strong>Next</strong>3.2. Configuring Host Names Using hostnamectl</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Network_Bonding.html b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Network_Bonding.html
new file mode 100644
index 0000000..6f8858d
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Network_Bonding.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 4. Configure Network Bonding</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="part-Networking.html" title="Part I. Networking" /><link rel="prev" href="sec-hostnamectl-Online_Documentation.html" title="3.4.2. Online Documentation" /><link rel="next" href="sec-Creating_a_Bond_Connection_Using_a_GUI.html" title="4.2. Creating a Bond Connection Using a GUI" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-hostnamectl-Online_Documentation.
html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Creating_a_Bond_Connection_Using_a_GUI.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-Configure_Network_Bonding" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 4. Configure Network Bonding</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Configure_Network_Bonding.html#sec-Bond-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces">4.1. Understanding the Default Behavior of Master and Slave Interfaces</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Bond_Connection_Using_a_GUI.html">4.2. Creating a Bond Connection Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Creating_a_Bond_Connection_Using_a_GUI.html#sec-Establishing_a_Bond_Connection">4.2.1. Establishing a Bond Connection</a></span></dt></dl></dd><dt><span class="section"><a href="
sec-Network_Bonding_Using_the_Command_Line_Interface.html">4.3. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Network_Bonding_Using_the_Command_Line_Interface.html#sec-Check_if_Bonding_Kernel_Module_is_Installed">4.3.1. Check if Bonding Kernel Module is Installed</a></span></dt><dt><span class="section"><a href="sec-Create_a_Channel_Bonding_Interface.html">4.3.2. Create a Channel Bonding Interface</a></span></dt><dt><span class="section"><a href="sec-Creating_SLAVE_Interfaces.html">4.3.3. Creating SLAVE Interfaces</a></span></dt><dt><span class="section"><a href="sec-Activating_a_Channel_Bond.html">4.3.4. Activating a Channel Bond</a></span></dt><dt><span class="section"><a href="sec-Creating_Multiple_Bonds.html">4.3.5. Creating Multiple Bonds</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_Channel_Bonding.html">4.4. Using Channel Bonding</a></span></dt><dd><dl><dt><span class="section"><a href="sec
-Using_Channel_Bonding.html#s3-modules-bonding-directives">4.4.1. Bonding Module Directives</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli.html">4.5. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="sec-Configure_Network_Bonding-additional_resources.html">4.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_Network_Bonding-additional_resources.html#sec-Configure_Network_Bonding-docs-inst">4.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-Configure_Network_Bonding_Online_Documentation.html">4.6.2. Online Documentation</a></span></dt></dl></dd></dl></div><div class="para">
+ Fedora allows administrators to bind multiple network interfaces together into a single, bonded, channel. Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The use of direct cable connections without network switches is not supported for bonding. The failover mechanisms described here will not work as expected without the presence of network switches.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The active-backup, balance-tlb and balance-alb modes do not require any specific configuration of the switch. Other bonding modes require configuring the switch to aggregate the links. For example, a Cisco switch requires EtherChannel for Modes 0, 2, and 3, but for Mode 4 LACP and EtherChannel are required. See the documentation supplied with your switch and see <a href="https://www.kernel.org/doc/Documentation/networking/bonding.txt">https://www.kernel.org/doc/Documentation/networking/bonding.txt</a>
+ </div></div></div><div class="section" id="sec-Bond-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.1. Understanding the Default Behavior of Master and Slave Interfaces</h2></div></div></div><div class="para">
+ When controlling bonded slave interfaces using the <code class="systemitem">NetworkManager</code> daemon, and especially when fault finding, keep the following in mind:
+ <div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Starting the master interface does not automatically start the slave interfaces.
+ </div></li><li class="listitem"><div class="para">
+ Starting a slave interface always starts the master interface.
+ </div></li><li class="listitem"><div class="para">
+ Stopping the master interface also stops the slave interfaces.
+ </div></li><li class="listitem"><div class="para">
+ A master without slaves can start static <code class="systemitem">IP</code> connections.
+ </div></li><li class="listitem"><div class="para">
+ A master without slaves waits for slaves when starting <code class="systemitem">DHCP</code> connections.
+ </div></li><li class="listitem"><div class="para">
+ A master with a <code class="systemitem">DHCP</code> connection waiting for slaves completes when a slave with a carrier is added.
+ </div></li><li class="listitem"><div class="para">
+ A master with a <code class="systemitem">DHCP</code> connection waiting for slaves continues waiting when a slave without a carrier is added.
+ </div></li></ol></div>
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-hostnamectl-Online_Documentation.html"><strong>Prev</strong>3.4.2. Online Documentation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Creating_a_Bond_Connection_Using_a_GUI.html"><strong>Next</strong>4.2. Creating a Bond Connection Using a GUI</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Network_Bridging.html b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Network_Bridging.html
new file mode 100644
index 0000000..ba0cc68
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Network_Bridging.html
@@ -0,0 +1,91 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 6. Configure Network Bridging</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="part-Networking.html" title="Part I. Networking" /><link rel="prev" href="sec-teamd_docs-online.html" title="5.14.2. Online Documentation" /><link rel="next" href="sec-Network_Bridging_Using_the_Command_Line_Interface.html" title="6.2. Using the Command Line Interface (CLI)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-teamd_docs-online.html"><strong>Prev
</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Bridging_Using_the_Command_Line_Interface.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-Configure_Network_Bridging" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 6. Configure Network Bridging</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Configure_Network_Bridging.html#sec-Configure_Network_Bridging_Using_a_GUI">6.1. Configure Network Bridging Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Network_Bridging.html#sec-Establishing_a_Bridge_Connection">6.1.1. Establishing a Bridge Connection</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Network_Bridging_Using_the_Command_Line_Interface.html">6.2. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Network_Bridging_Using_the_Command_Line_Interface
.html#sec-Check_if_Bridging_Kernel_Module_is_Installed">6.2.1. Check if Bridging Kernel Module is Installed</a></span></dt><dt><span class="section"><a href="sec-Create_a_Network_Bridge.html">6.2.2. Create a Network Bridge</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html">6.3. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="sec-Network_Bridging-additional_resources.html">6.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Network_Bridging-additional_resources.html#sec-Network_Bridging-docs-inst">6.4.1. Installed Documentation</a></span></dt></dl></dd></dl></div><div class="para">
+ A network bridge is a link-layer device which forwards traffic between networks based on MAC addresses. It makes forwarding decisions based on a table of MAC addresses which it builds by listening to network traffic and thereby learning what hosts are connected to each network. A software bridge can be used within a Linux host in order to emulate a hardware bridge, for example in virtualization applications for sharing a NIC with one or more virtual NICs.
+ </div><div class="para">
+ Note that a bridge cannot be established over Wi-Fi networks operating in <em class="firstterm">Ad-Hoc</em> or <em class="firstterm">Infrastructure</em> modes. This is due to the IEEE 802.11 standard that specifies the use of 3-address frames in Wi-Fi for the efficient use of airtime. A system configured to be an <em class="firstterm">access point</em> (<acronym class="acronym">AP</acronym>) running the <code class="systemitem">hostapd</code> can support the necessary 4-address frames.
+ </div><div class="section" id="sec-Configure_Network_Bridging_Using_a_GUI"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. Configure Network Bridging Using a GUI</h2></div></div></div><div class="para">
+ When starting a bridge interface, <span class="application"><strong>NetworkManager</strong></span> waits for at least one port to enter the <span class="quote">“<span class="quote">forwarding</span>”</span> state before beginning any network-dependent <code class="systemitem">IP</code> configuration such as <code class="systemitem">DHCP</code> or <code class="systemitem">IPv6</code> autoconfiguration. Static <code class="systemitem">IP</code> addressing is allowed to proceed before any slaves or ports are connected or begin forwarding packets.
+ </div><div class="section" id="sec-Establishing_a_Bridge_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.1.1. Establishing a Bridge Connection</h3></div></div></div><div class="procedure" id="procedure-Adding_a_New_Bridge_Connection"><h6>Procedure 6.1. Adding a New Bridge Connection</h6><div class="para">
+ You can configure a new Bridge connection by opening the <span class="guilabel"><strong>Network</strong></span> window and selecting the plus symbol below the menu.
+ </div><ol class="1"><li class="step"><div class="para">
+ To use the graphical <span class="application"><strong>Network</strong></span> settings tool, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the plus symbol below the menu. The <span class="guilabel"><strong>Add Network Connection</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Bridge</strong></span> menu entry. The <span class="guilabel"><strong>Editing Bridge connection <em class="replaceable"><code>1</code></em></strong></span> window appears.
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_Bridge_Connection"><h6>Procedure 6.2. Editing an Existing Bridge Connection</h6><div class="para">
+ You can configure an existing bridge connection by opening the <span class="guilabel"><strong>Network</strong></span> window and selecting the name of the connection from the list. Then click the <span class="guibutton"><strong>Edit</strong></span> button.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Bridge</strong></span> connection you want to edit from the left hand menu.
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guilabel"><strong>Options</strong></span> button.
+ </div></li></ol></div><h4 id="bh-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-bridge">Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Five settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types, see the <span class="guilabel"><strong>General</strong></span> tab:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the menu of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to this network when it is available</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>All users may connect to this network</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="sec-System-wide_and_Private_Connection_Profiles.html">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to VPN when using this connection</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to a VPN connection when it is available. Select the VPN from the dropdown menu.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Firewall Zone</strong></span> — Select the Firewall Zone from the dropdown menu.
+ </div></li></ul></div><div class="section" id="sec-Configuring_the_Bridge_Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">6.1.1.1. Configuring the Bridge Tab</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Interface name</strong></span> </span></dt><dd><div class="para">
+ The name of the interface to the bridge.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Bridged connections</strong></span> </span></dt><dd><div class="para">
+ One or more slave interfaces.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Aging time</strong></span> </span></dt><dd><div class="para">
+ The time, in seconds, a MAC address is kept in the MAC address forwarding database.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Enable STP (Spanning Tree Protocol)</strong></span> </span></dt><dd><div class="para">
+ If required, select the check box to enable <code class="systemitem">STP</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Priority</strong></span> </span></dt><dd><div class="para">
+ The bridge priority; the bridge with the lowest priority will be elected as the root bridge.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Forward delay</strong></span> </span></dt><dd><div class="para">
+ The time, in seconds, spent in both the Listening and Learning states before entering the Forwarding state. The default is 15 seconds.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Hello time</strong></span> </span></dt><dd><div class="para">
+ The time interval, in seconds, between sending configuration information in bridge protocol data units (BPDU).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Max age</strong></span> </span></dt><dd><div class="para">
+ The maximum time, in seconds, to store the configuration information from BPDUs. This value should be twice the Hello Time plus 1 but less than twice the Forwarding delay minus 1.
+ </div></dd></dl></div><div class="figure" id="exam--Establishing_a_Bridge_Connection"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Editing-Bridge-Connection-1_Gnome3.png"><img src="images/Editing-Bridge-Connection-1_Gnome3.png" alt="Editing Bridge Connection 1" /><div class="longdesc"><div class="para">
+ A screen shot of the Editing Bridge Connection 1
+ </div></div></div></div><h6>Figure 6.1. Editing Bridge Connection 1</h6></div><br class="figure-break" /><div class="procedure" id="procedure-Adding_a_Slave_Interface_to_a_Bridge"><h6>Procedure 6.3. Adding a Slave Interface to a Bridge</h6><ol class="1"><li class="step"><div class="para">
+ To add a port to a bridge, select the <span class="guilabel"><strong>Bridge</strong></span> tab in the <span class="guilabel"><strong>Editing Bridge connection <em class="replaceable"><code>1</code></em></strong></span> window. If necessary, open this window by following the procedure in <a class="xref" href="ch-Configure_Network_Bridging.html#procedure-Editing_an_Existing_Bridge_Connection">Procedure 6.2, “Editing an Existing Bridge Connection”</a>.
+ </div></li><li class="step"><div class="para">
+ Click <span class="guibutton"><strong>Add</strong></span>. The <span class="guilabel"><strong>Choose a Connection Type</strong></span> menu appears.
+ </div></li><li class="step"><div class="para">
+ Select the type of connection to be created from the list. Click <span class="guilabel"><strong>Create</strong></span>. A window appropriate to the connection type selected appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Bridge Port</strong></span> tab. Configure <span class="guilabel"><strong>Priority</strong></span> and <span class="guilabel"><strong>Path cost</strong></span> as required. Note the STP priority for a bridge port is limited by the Linux kernel. Although the standard allows a range of <code class="literal">0</code> to <code class="literal">255</code>, Linux only allows <code class="literal">0</code> to <code class="literal">63</code>. The default is <code class="literal">32</code> in this case.
+ </div></li><li class="step"><div class="para">
+ If required, select the <span class="guilabel"><strong>Hairpin mode</strong></span> check box to enable forwarding of frames for external processing. Also known as <em class="firstterm">virtual Ethernet port aggregator</em> (<acronym class="acronym">VEPA</acronym>) mode.
+ </div></li></ol></div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ An Ethernet slave, click the <span class="guilabel"><strong>Ethernet</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_a_Wired_Ethernet_Connection.html#sec-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-wired">Section 2.2.5.1, “Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings”</a>, or;
+ </div></li><li class="listitem"><div class="para">
+ A Bond slave, click the <span class="guilabel"><strong>Bond</strong></span> tab and proceed to <a class="xref" href="sec-Creating_a_Bond_Connection_Using_a_GUI.html#sec-Configuring_the_Bond_Tab">Section 4.2.1.1, “Configuring the Bond Tab”</a>, or;
+ </div></li><li class="listitem"><div class="para">
+ A Team slave, click the <span class="guilabel"><strong>Team</strong></span> tab and proceed to <a class="xref" href="sec-Creating_a_Network_Team_Using_a_GUI.html#sec-Configuring_the_Team_Tab">Section 5.9.1.1, “Configuring the Team Tab”</a>, or;
+ </div></li><li class="listitem"><div class="para">
+ An VLAN slave, click the <span class="guilabel"><strong>VLAN</strong></span> tab and proceed to <a class="xref" href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html#sec-Configuring_the_VLAN_Tab">Section 7.2.1.1, “Configuring the VLAN Tab”</a>, or;
+ </div></li></ul></div><h5 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-bridge">Saving Your New (or Modified) Connection and Making Further Configurations</h5><div class="para">
+ Once you have finished editing your new bridge connection, click the <span class="guibutton"><strong>Save</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network</strong></span> window and clicking <span class="guilabel"><strong>Options</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>, or;
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv6</code> settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv6_Settings">Section 2.2.10.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-teamd_docs-online.html"><strong>Prev</strong>5.14.2. Online Documentation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Bridging_Using_the_Command_Line_Interface.html"><strong>Next</strong>6.2. Using the Command Line Interface (CLI)</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Network_Teaming.html b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Network_Teaming.html
new file mode 100644
index 0000000..c091c0a
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Network_Teaming.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 5. Configure Network Teaming</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="part-Networking.html" title="Part I. Networking" /><link rel="prev" href="sec-Configure_Network_Bonding_Online_Documentation.html" title="4.6.2. Online Documentation" /><link rel="next" href="sec-Comparison_of_Network_Teaming_to_Bonding.html" title="5.2. Comparison of Network Teaming to Bonding" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_Netwo
rk_Bonding_Online_Documentation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Comparison_of_Network_Teaming_to_Bonding.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-Configure_Network_Teaming" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 5. Configure Network Teaming</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Configure_Network_Teaming.html#sec-Understanding_Network_Teaming">5.1. Understanding Network Teaming</a></span></dt><dt><span class="section"><a href="sec-Comparison_of_Network_Teaming_to_Bonding.html">5.2. Comparison of Network Teaming to Bonding</a></span></dt><dt><span class="section"><a href="sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces.html">5.3. Understanding the Default Behavior of Master and Slave Interfaces</a></span></dt><dt><span class="section"><a href="sec-Understanding_the_Netwo
rk_Teaming_Daemon_and_the_Runners.html">5.4. Understanding the Network Teaming Daemon and the "Runners"</a></span></dt><dt><span class="section"><a href="sec-Install_the_Network_Teaming_Daemon.html">5.5. Install the Network Teaming Daemon</a></span></dt><dt><span class="section"><a href="sec-Converting_a_Bond_to_a_Team.html">5.6. Converting a Bond to a Team</a></span></dt><dt><span class="section"><a href="sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team.html">5.7. Selecting Interfaces to Use as Ports for a Network Team</a></span></dt><dt><span class="section"><a href="sec-Selecting_Network_Team_Configuration_Methods.html">5.8. Selecting Network Team Configuration Methods</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Network_Team_Using_a_GUI.html">5.9. Creating a Network Team Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Creating_a_Network_Team_Using_a_GUI.html#sec-Establishing_a_Team_Connection">5.9.1. Establishing a
Team Connection</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_a_Network_Team_Using-the_Command_Line.html">5.10. Configure a Network Team Using the Command Line</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_a_Network_Team_Using-the_Command_Line.html#sec-Creating_a_Network_Team_Using_teamd">5.10.1. Creating a Network Team Using teamd</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Network_Team_Using_ifcfg_Files.html">5.10.2. Creating a Network Team Using ifcfg Files</a></span></dt><dt><span class="section"><a href="sec-Add_a_port_to_a_Network_Team_Using_iputils.html">5.10.3. Add a Port to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="sec-Listing_the_ports_of_a_Team_Using_teamnl.html">5.10.4. Listing the ports of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="sec-Configuring_Options_of_a_Team_Using_teamnl.html">5.10.5. Configuring Options of a Team Usin
g teamnl</a></span></dt><dt><span class="section"><a href="sec-Add_an_address_to_a_Network_Team_Using_iputils.html">5.10.6. Add an Address to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils.html">5.10.7. Bring up an Interface to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl.html">5.10.8. Viewing the Active Port Options of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl.html">5.10.9. Setting the Active Port Options of a Team Using teamnl</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Controlling_teamd_with_teamdctl.html">5.11. Controlling teamd with teamdctl</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Controlling_teamd_with_teamdctl.html#sec-Add_a_port_to_a_Network_Team">5.11.1. Add a Port to a Net
work Team</a></span></dt><dt><span class="section"><a href="sec-Remove_a_Port_From_a_Network_Team.html">5.11.2. Remove a Port From a Network Team</a></span></dt><dt><span class="section"><a href="sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team.html">5.11.3. Apply a Configuration to a Port in a Network Team</a></span></dt><dt><span class="section"><a href="sec-View_the_Configuration_of_a_Port_in_a_Network_Team.html">5.11.4. View the Configuration of a Port in a Network Team</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_teamd_Runners.html">5.12. Configure teamd Runners</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_teamd_Runners.html#sec-Configure_the_broadcast_Runner">5.12.1. Configure the broadcast Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_the_random_Runner.html">5.12.2. Configure the random Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_the_roundrobin_Runner.html"
>5.12.3. Configure the roundrobin Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_the_activebackup_Runner.html">5.12.4. Configure the activebackup Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_the_loadbalance_Runner.html">5.12.5. Configure the loadbalance Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_the_LACP_Runner.html">5.12.6. Configure the LACP (802.3ad) Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_Monitoring_of_the_Link_State.html">5.12.7. Configure Monitoring of the Link State</a></span></dt><dt><span class="section"><a href="sec-Configure_Port_Selection_Override.html">5.12.8. Configure Port Selection Override</a></span></dt><dt><span class="section"><a href="sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm.html">5.12.9. Configure BPF-based Tx Port Selectors</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_Network_Teaming_U
sing_nmcli.html">5.13. Configure Network Teaming Using nmcli</a></span></dt><dt><span class="section"><a href="sec-Network_Teaming-additional_resources.html">5.14. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Network_Teaming-additional_resources.html#sec-teamd-docs-inst">5.14.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-teamd_docs-online.html">5.14.2. Online Documentation</a></span></dt></dl></dd></dl></div><div class="section" id="sec-Understanding_Network_Teaming"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. Understanding Network Teaming</h2></div></div></div><div class="para">
+ The combining or aggregating together of network links in order to provide a logical link with higher throughput, or to provide redundancy, is known by many names such as <span class="quote">“<span class="quote">channel bonding</span>”</span>, <span class="quote">“<span class="quote">Ethernet bonding</span>”</span>, <span class="quote">“<span class="quote">port trunking</span>”</span>, <span class="quote">“<span class="quote">channel teaming</span>”</span>, <span class="quote">“<span class="quote">NIC teaming</span>”</span>, <span class="quote">“<span class="quote">link aggregation</span>”</span>, and so on. This concept as originally implemented in the Linux kernel is widely referred to as <span class="quote">“<span class="quote">bonding</span>”</span>. The term Network Teaming has been chosen to refer to this new implementation of the concept. The existing bonding driver is unaffected, Network Teaming is offered as an alternative and does not
replace bonding in Fedora.
+ </div><div class="para">
+ Network Teaming, or Team, is designed to implement the concept in a different way by providing a small kernel driver to implement the fast handling of packet flows, and various user-space applications to do everything else in user space. The driver has an <em class="firstterm">Application Programming Interface</em> (<acronym class="acronym">API</acronym>), referred to as <span class="quote">“<span class="quote">Team Netlink API</span>”</span>, which implements Netlink communications. User-space applications can use this API to communicate with the driver. A library, referred to as <span class="quote">“<span class="quote">lib</span>”</span>, has been provided to do user space wrapping of Team Netlink communications and RT Netlink messages. An application daemon, <code class="systemitem">teamd</code>, which uses Libteam lib is also provided. One instance of <code class="systemitem">teamd</code> can control one instance of the Team driver. The daemon implements the l
oad-balancing and active-backup logic, such as round-robin, by using additional code referred to as <span class="quote">“<span class="quote">runners</span>”</span>. By separating the code in this way, the Network Teaming implementation presents an easily extensible and scalable solution for load-balancing and redundancy requirements. For example, custom runners can be relatively easily written to implement new logic via <code class="systemitem">teamd</code>, and even <code class="systemitem">teamd</code> is optional, users can write their own application to use <span class="application"><strong>libteam</strong></span>.
+ </div><div class="para">
+ A tool to control a running instance of <code class="systemitem">teamd</code> using D-bus is provided by <span class="application"><strong>teamdctl</strong></span>. It provides a D-Bus wrapper around the <code class="systemitem">teamd</code> D-Bus API. By default, <code class="systemitem">teamd</code> listens and communicates using Unix Domain Sockets but still monitors D-Bus. This is to ensure that <code class="systemitem">teamd</code> can be used in environments where D-Bus is not present or not yet loaded. For example, when booting over <code class="systemitem">teamd</code> links D-Bus would not yet be loaded. The <span class="application"><strong>teamdctl</strong></span> tool can be used during run time to read the configuration, the state of link-watchers, check and change the state of ports, add and remove ports, and to change ports between active and backup states.
+ </div><div class="para">
+ Team Netlink API communicates with user-space applications using Netlink messages. The user-space library <span class="application"><strong>libteam</strong></span> does not directly interact with the API, but uses <span class="application"><strong>libnl</strong></span> or <span class="application"><strong>teamnl</strong></span> to interact with the driver API.
+ </div><div class="para">
+ To sum up, the instances of Team driver, running in the kernel, do not get configured or controlled directly. All configuration is done with the aid of user space applications, such as the <span class="application"><strong>teamd</strong></span> application. The application then directs the kernel driver part accordingly.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_Network_Bonding_Online_Documentation.html"><strong>Prev</strong>4.6.2. Online Documentation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Comparison_of_Network_Teaming_to_Bonding.html"><strong>Next</strong>5.2. Comparison of Network Teaming to Bonding</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Networking.html b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Networking.html
new file mode 100644
index 0000000..5fcf5a2
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Configure_Networking.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 2. Configure Networking</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="part-Networking.html" title="Part I. Networking" /><link rel="prev" href="sec-Introduction_to_Fedora_Networking-additional_resources.html" title="1.8. Additional Resources" /><link rel="next" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html" title="2.2. Using NetworkManager with the GNOME Graphical User Interface" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previo
us"><a accesskey="p" href="sec-Introduction_to_Fedora_Networking-additional_resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-Configure_Networking" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. Configure Networking</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Configure_Networking.html#sec-Static_and_Dynamic_Interface_Settings">2.1. Static and Dynamic Interface Settings</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Networking.html#sec-When_to_Use_Static_Network_Interface_Settings">2.1.1. When to Use Static Network Interface Settings</a></span></dt><dt><span class="section"><a href="ch-Configure_Networking.html#sec-When_to_Use_Dynamic_Interface_Settings">2.1.2. When to Use Dynamic Interface
Settings</a></span></dt><dt><span class="section"><a href="ch-Configure_Networking.html#sec-Selecting_Network_Configuration_Methods">2.1.3. Selecting Network Configuration Methods</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html">2.2. Using NetworkManager with the GNOME Graphical User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html#sec-Connecting_to_a_Network_Using_a_GUI">2.2.1. Connecting to a Network Using a GUI</a></span></dt><dt><span class="section"><a href="sec-Configuring_New_and_Editing_Existing_Connections.html">2.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="sec-Connecting_to_a_Network_Automatically.html">2.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="sec-System-wide_and_Private_Connection_Pro
files.html">2.2.4. System-wide and Private Connection Profiles</a></span></dt><dt><span class="section"><a href="sec-Configuring_a_Wired_Ethernet_Connection.html">2.2.5. Configuring a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="sec-Configuring_a_Wi-Fi_Connection.html">2.2.6. Configuring a Wi-Fi Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_VPN_Connection.html">2.2.7. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_Mobile_Broadband_Connection.html">2.2.8. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_DSL_Connection.html">2.2.9. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="sec-Configuring_Connection_Settings.html">2.2.10. Configuring Connection Settings</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_the_Command_Line_Interface.html">2.3. U
sing the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_the_Command_Line_Interface.html#sec-Configuring_a_Network_Interface_Using_ifcg_Files">2.3.1. Configuring a Network Interface Using ifcfg Files</a></span></dt><dt><span class="section"><a href="sec-Configuring_a_Network_Interface_Using_ip_commands.html">2.3.2. Configuring a Network Interface Using ip Commands</a></span></dt><dt><span class="section"><a href="sec-Static-Routes_and_the_Default_Gateway.html">2.3.3. Static Routes and the Default Gateway</a></span></dt><dt><span class="section"><a href="sec-Configuring_Static_Routes_in_ifcfg_files.html">2.3.4. Configuring Static Routes in ifcfg files</a></span></dt><dt><span class="section"><a href="sec-Configuring_IPv6_Tokenized_Interface_Identifiers.html">2.3.5. Configuring IPv6 Tokenized Interface Identifiers</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.htm
l">2.4. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html#sec-Understanding_the_nmcli_Options">2.4.1. Understanding the nmcli Options</a></span></dt><dt><span class="section"><a href="sec-Connecting_to_a_Network_Using_nmcli.html">2.4.2. Connecting to a Network Using nmcli</a></span></dt><dt><span class="section"><a href="sec-Configuring_Static_Routes_Using_nmcli.html">2.4.3. Configuring Static Routes Using nmcli</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_Networking-additional_resources.html">2.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_Networking-additional_resources.html#sec-Configure_Networking-docs-inst">2.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-Configure_Networking_Online_Documentation.html">2.5.2. Online Documentation</a></span></d
t></dl></dd></dl></div><div class="section" id="sec-Static_and_Dynamic_Interface_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.1. Static and Dynamic Interface Settings</h2></div></div></div><div class="para">
+ When to use static addressing and when to use dynamic addressing? These decisions are subjective, they depend on your accessed needs, your specific requirements. Having a policy, documenting it, and applying it consistently are usually more important than the specific decisions you make. In a traditional company LAN, this is an easier decision to make as you typically have fewer servers than other hosts. Provisioning and installation tools make providing static configurations to new hosts easy and using such tools will change your work flow and requirements. The following two sections are intended to provide guidance to those who have not already been through this decision-making process. For more information on automated configuration and management, see the <span class="application"><strong>OpenLMI</strong></span> section in the <em class="citetitle">System Administrators Guide</em>. The <em class="citetitle">System Installation Guide</em> documents the use of <span cla
ss="application"><strong>kickstart</strong></span> which can also be used for automating the assignment of network settings.
+ </div><div class="section" id="sec-When_to_Use_Static_Network_Interface_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.1. When to Use Static Network Interface Settings</h3></div></div></div><div class="para">
+
+ </div><div class="para">
+ Use static <code class="systemitem">IP</code> addressing on those servers and devices whose network availability you want to ensure when automatic assignment methods, such as <code class="systemitem">DHCP</code>, fail. <code class="systemitem">DHCP</code>, <code class="systemitem">DNS</code>, and authentication servers are typical examples. Interfaces for out-of-band management devices are also worth configuring with static settings as these devices are supposed to work, as far as is possible, independently of other network infrastructure.
+ </div><div class="para">
+ For hosts which are not considered vital, but for which static <code class="systemitem">IP</code> addressing is still considered desirable, use an automated provisioning method when possible. For example, <code class="systemitem">DHCP</code> servers can be configured to provide the same <code class="systemitem">IP</code> address to the same host every time. This method could be used for communal printers for example.
+ </div><div class="para">
+ All the configuration tools listed in <a class="xref" href="ch-Configure_Networking.html#sec-Selecting_Network_Configuration_Methods">Section 2.1.3, “Selecting Network Configuration Methods”</a> allow assigning static <code class="systemitem">IP</code> addresses manually. The <span class="application"><strong>nmcli</strong></span> tool is also suitable for use with scripted assignment of network configuration.
+ </div></div><div class="section" id="sec-When_to_Use_Dynamic_Interface_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.2. When to Use Dynamic Interface Settings</h3></div></div></div><div class="para">
+
+ </div><div class="para">
+ Enable and use dynamic assignment of <code class="systemitem">IP</code> addresses and other network information whenever there is no compelling reason not to. The time saved in planning and documenting manual settings can be better spent elsewhere. The <em class="firstterm">dynamic host control protocol</em> (<acronym class="acronym">DHCP</acronym>) is a traditional method of dynamically assigning network configurations to hosts. See <a class="xref" href="ch-DHCP_Servers.html#sec-dhcp-why">Section 9.1, “Why Use DHCP?”</a> for more information on this subject.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> will by default call the <code class="systemitem">DHCP</code> client, <span class="application"><strong>dhclient</strong></span>, when a profile has been set to obtain addresses automatically, or when an interface configuration file has BOOTPROTO set to <code class="literal">dhcp</code>. Where <code class="systemitem">DHCP</code> is required, an instance of <code class="systemitem">dhclient</code> is started for every Internet protocol, <code class="systemitem">IPv4</code> and <code class="systemitem">IPv6</code>, on an interface. Where <span class="application"><strong>NetworkManager</strong></span> is not running, or not managing an interface, then the legacy network service will call instances of <code class="systemitem">dhclient</code> as required.
+ </div></div><div class="section" id="sec-Selecting_Network_Configuration_Methods"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.3. Selecting Network Configuration Methods</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ To configure a network using graphical user interface tools, proceed to <a class="xref" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html">Section 2.2, “Using NetworkManager with the GNOME Graphical User Interface”</a>
+ </div></li><li class="listitem"><div class="para">
+ To configure a network interface manually, see <a class="xref" href="sec-Using_the_Command_Line_Interface.html">Section 2.3, “Using the Command Line Interface (CLI)”</a>.
+ </div></li><li class="listitem"><div class="para">
+ To configure an interface using <span class="application"><strong>NetworkManager</strong></span>'s command-line tool, <span class="application"><strong>nmcli</strong></span>, proceed to <a class="xref" href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html">Section 2.4, “Using the NetworkManager Command Line Tool, nmcli”</a>
+ </div></li></ul></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Introduction_to_Fedora_Networking-additional_resources.html"><strong>Prev</strong>1.8. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html"><strong>Next</strong>2.2. Using NetworkManager with the GNOME Graphica...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Consistent_Network_Device_Naming.html b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Consistent_Network_Device_Naming.html
new file mode 100644
index 0000000..bb94261
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Consistent_Network_Device_Naming.html
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 8. Consistent Network Device Naming</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="part-Networking.html" title="Part I. Networking" /><link rel="prev" href="sec-Configure_802_1Q_VLAN_Tagging-additional_resources.html" title="7.5. Additional Resources" /><link rel="next" href="sec-Understanding_the_Device_Renaming_Procedure.html" title="8.2. Understanding the Device Renaming Procedure" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configu
re_802_1Q_VLAN_Tagging-additional_resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Understanding_the_Device_Renaming_Procedure.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-Consistent_Network_Device_Naming" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 8. Consistent Network Device Naming</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Consistent_Network_Device_Naming.html#sec-Naming_Schemes_Hierarchy">8.1. Naming Schemes Hierarchy</a></span></dt><dt><span class="section"><a href="sec-Understanding_the_Device_Renaming_Procedure.html">8.2. Understanding the Device Renaming Procedure</a></span></dt><dt><span class="section"><a href="sec-Understanding_the_Predictable_Network_Interface_Device_Names.html">8.3. Understanding the Predictable Network Interface Device Names</a></span></dt><dt><span class="section"><a href="sec-Naming
_Scheme_for_Network_Devices_Available_for_Linux_on_System_z.html">8.4. Naming Scheme for Network Devices Available for Linux on System z</a></span></dt><dt><span class="section"><a href="sec-Naming_Scheme_for_VLAN_Interfaces.html">8.5. Naming Scheme for VLAN Interfaces</a></span></dt><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming_Using_biosdevname.html">8.6. Consistent Network Device Naming Using biosdevname</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming_Using_biosdevname.html#sec-Consistent_Network_Device_Naming-System_Requirements">8.6.1. System Requirements</a></span></dt><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming-Enabling_and_Disabling.html">8.6.2. Enabling and Disabling the Feature</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming-Notes.html">8.7. Notes for Administrators</a></span></dt><dt><span class="section"><a href="se
c-Controlling_the_Selection_of_Network_Device_Names.html">8.8. Controlling the Selection of Network Device Names</a></span></dt><dt><span class="section"><a href="sec-Disabling_Consistent_Network_Device_Naming.html">8.9. Disabling Consistent Network Device Naming</a></span></dt><dt><span class="section"><a href="sec_Troubleshooting_Network_Device_Naming.html">8.10. Troubleshooting Network Device Naming</a></span></dt><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming-additional_resources.html">8.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming-additional_resources.html#sec-Consistent_Network_Device_Naming-docs-inst">8.11.1. Installed Documentation</a></span></dt></dl></dd></dl></div><div class="para">
+ Fedora 20 provides methods for consistent and predictable network device naming for network interfaces. These features change the name of network interfaces on a system in order to make locating and differentiating the interfaces easier.
+ </div><div class="para">
+ Traditionally, network interfaces in Linux are enumerated as <code class="interfacename">eth[0123…]</code>, but these names do not necessarily correspond to actual labels on the chassis. Modern server platforms with multiple network adapters can encounter non-deterministic and counter-intuitive naming of these interfaces. This affects both network adapters embedded on the motherboard (<em class="firstterm">Lan-on-Motherboard</em>, or <em class="firstterm"><acronym class="acronym">LOM</acronym></em>) and add-in (single and multiport) adapters.
+ </div><div class="para">
+ In Fedora 20, <span class="application"><strong>udev</strong></span> supports a number of different naming schemes. The default is to assign fixed names based on firmware, topology, and location information. This has the advantage that the names are fully automatic, fully predictable, that they stay fixed even if hardware is added or removed (no re-enumeration takes place), and that broken hardware can be replaced seamlessly. The disadvantage is that they are sometimes harder to read than the <span class="interface">eth0</span> or <span class="interface">wlan0</span> names traditionally used. For example: <span class="interface">enp5s0</span>.
+ </div><div class="section" id="sec-Naming_Schemes_Hierarchy"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.1. Naming Schemes Hierarchy</h2></div></div></div><div class="para">
+ By default, <code class="systemitem">systemd</code> will name interfaces using the following policy to apply the supported naming schemes:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Scheme 1:</strong></span> Names incorporating Firmware or BIOS provided index numbers for on-board devices (example: <code class="literal">eno1</code>), are applied if that information from the firmware or BIOS is applicable and available, else falling back to scheme 2.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Scheme 2:</strong></span> Names incorporating Firmware or BIOS provided PCI Express hotplug slot index numbers (example: <code class="literal">ens1</code>) are applied if that information from the firmware or BIOS is applicable and available, else falling back to scheme 3.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Scheme 3:</strong></span> Names incorporating physical location of the connector of the hardware (example: <code class="literal">enp2s0</code>), are applied if applicable, else falling directly back to scheme 5 in all other cases.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Scheme 4:</strong></span> Names incorporating interface's MAC address (example: <code class="literal">enx78e7d1ea46da</code>), is not used by default, but is available if the user chooses.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Scheme 5:</strong></span> The traditional unpredictable kernel naming scheme, is used if all other methods fail (example: <code class="literal">eth0</code>).
+ </div></li></ul></div>
+ </div><div class="para">
+ This policy, the procedure outlined above, is the default. If the system has <span class="application"><strong>biosdevname</strong></span> enabled, it will be used. Note that enabling <span class="application"><strong>biosdevname</strong></span> requires passing <code class="command">biosdevname=1</code> as a command-line parameter except in the case of a Dell system, where <span class="application"><strong>biosdevname</strong></span> will be used by default as long as it is installed. If the user has added <span class="application"><strong>udev</strong></span> rules which change the name of the kernel devices, those rules will take precedence.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_802_1Q_VLAN_Tagging-additional_resources.html"><strong>Prev</strong>7.5. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Understanding_the_Device_Renaming_Procedure.html"><strong>Next</strong>8.2. Understanding the Device Renaming Procedure</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/ch-DHCP_Servers.html b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-DHCP_Servers.html
new file mode 100644
index 0000000..6f3c8e9
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-DHCP_Servers.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 9. DHCP Servers</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="part-Servers.html" title="Part II. Servers" /><link rel="prev" href="part-Servers.html" title="Part II. Servers" /><link rel="next" href="sec-dhcp-configuring-server.html" title="9.2. Configuring a DHCP Server" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Servers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-dhcp-config
uring-server.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-DHCP_Servers" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 9. DHCP Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-DHCP_Servers.html#sec-dhcp-why">9.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="sec-dhcp-configuring-server.html">9.2. Configuring a DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="sec-dhcp-configuring-server.html#config-file">9.2.1. Configuration File</a></span></dt><dt><span class="section"><a href="lease-database.html">9.2.2. Lease Database</a></span></dt><dt><span class="section"><a href="ch09s02s03.html">9.2.3. Starting and Stopping the Server</a></span></dt></dl></dd><dt><span class="section"><a href="dhcp-relay-agent.html">9.3. DHCP Relay Agent</a></span></dt><dd><dl><dt><span class="section"><a href="dhcp-relay-agent.html#sec-Configur
e_dhcrelay_as_a_DHCPv4_and_BOOTP_relay_agent">9.3.1. Configure dhcrelay as a DHCPv4 and BOOTP relay agent</a></span></dt><dt><span class="section"><a href="sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent.html">9.3.2. Configure dhcrelay as a DHCPv6 relay agent</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_a_Multihomed_DHCP_Server.html">9.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configuring_a_Multihomed_DHCP_Server.html#sec-dns_Host_Configuration">9.4.1. Host Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="sec-dhcp_for_ipv6_dhcpv6.html">9.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="sec-dhcp-additional-resources.html">9.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-dhcp-additional-resources.html#sec-dhcp-installed-docs">9.6.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="
idm225445398336" class="indexterm"></a><a id="idm225416633488" class="indexterm"></a><div class="para">
+ Dynamic Host Configuration Protocol (<acronym class="acronym">DHCP</acronym>) is a network protocol that automatically assigns TCP/IP information to client machines. Each <code class="systemitem">DHCP</code> client connects to the centrally located <code class="systemitem">DHCP</code> server, which returns the network configuration (including the <code class="systemitem">IP</code> address, gateway, and <code class="systemitem">DNS</code> servers) of that client.
+ </div><div class="section" id="sec-dhcp-why"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.1. Why Use DHCP?</h2></div></div></div><a id="idm225455543792" class="indexterm"></a><div class="para">
+ <code class="systemitem">DHCP</code> is useful for automatic configuration of client network interfaces. When configuring the client system, you can choose <code class="systemitem">DHCP</code> instead of specifying an <code class="systemitem">IP</code> address, netmask, gateway, or <code class="systemitem">DNS</code> servers. The client retrieves this information from the <code class="systemitem">DHCP</code> server. <code class="systemitem">DHCP</code> is also useful if you want to change the <code class="systemitem">IP</code> addresses of a large number of systems. Instead of reconfiguring all the systems, you can just edit one configuration file on the server for the new set of <code class="systemitem">IP</code> addresses. If the <code class="systemitem">DNS</code> servers for an organization changes, the changes happen on the <code class="systemitem">DHCP</code> server, not on the <code class="systemitem">DHCP</code> clients. When you restart the network or reboot the
clients, the changes go into effect.
+ </div><div class="para">
+ If an organization has a functional <code class="systemitem">DHCP</code> server correctly connected to a network, laptops and other mobile computer users can move these devices from office to office.
+ </div><div class="para">
+ Note that administrators of <code class="systemitem">DNS</code> and <code class="systemitem">DHCP</code> servers, as well as any provisioning applications, should agree on the host name format used in an organization. See <a class="xref" href="ch-Configure_Host_Names.html#sec-Recommended_Naming_Practices">Section 3.1.1, “Recommended Naming Practices”</a> for more information on the format of host names.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Servers.html"><strong>Prev</strong>Part II. Servers</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-dhcp-configuring-server.html"><strong>Next</strong>9.2. Configuring a DHCP Server</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/ch-DNS_Servers.html b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-DNS_Servers.html
new file mode 100644
index 0000000..d717bda
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-DNS_Servers.html
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 10. DNS Servers</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="part-Servers.html" title="Part II. Servers" /><link rel="prev" href="sec-dhcp-additional-resources.html" title="9.6. Additional Resources" /><link rel="next" href="sec-BIND.html" title="10.2. BIND" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-dhcp-additional-resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-BIND.htm
l"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-DNS_Servers" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 10. DNS Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-DNS_Servers.html#sec-Introduction_to_DNS">10.1. Introduction to DNS</a></span></dt><dd><dl><dt><span class="section"><a href="ch-DNS_Servers.html#sec-dns-introduction-zones">10.1.1. Nameserver Zones</a></span></dt><dt><span class="section"><a href="ch-DNS_Servers.html#sec-dns-introduction-nameservers">10.1.2. Nameserver Types</a></span></dt><dt><span class="section"><a href="ch-DNS_Servers.html#sec-dns-introduction-bind">10.1.3. BIND as a Nameserver</a></span></dt></dl></dd><dt><span class="section"><a href="sec-BIND.html">10.2. BIND</a></span></dt><dd><dl><dt><span class="section"><a href="sec-BIND.html#sec-bind-empty-zones">10.2.1. Empty Zones</a></span></dt><dt><span class="section"><a href="sec-bi
nd-namedconf.html">10.2.2. Configuring the named Service</a></span></dt><dt><span class="section"><a href="sec-bind-zone.html">10.2.3. Editing Zone Files</a></span></dt><dt><span class="section"><a href="sec-bind-rndc.html">10.2.4. Using the rndc Utility</a></span></dt><dt><span class="section"><a href="sec-bind-dig.html">10.2.5. Using the dig Utility</a></span></dt><dt><span class="section"><a href="sec-bind-features.html">10.2.6. Advanced Features of BIND</a></span></dt><dt><span class="section"><a href="sec-bind-mistakes.html">10.2.7. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="sec-bind-additional-resources.html">10.2.8. Additional Resources</a></span></dt></dl></dd></dl></div><a id="idm225489671216" class="indexterm"></a><a id="idm225483243760" class="indexterm"></a><div class="para">
+ <code class="systemitem">DNS</code> (Domain Name System), is a distributed database system that is used to associate host names with their respective <code class="systemitem">IP</code> addresses. For users, this has the advantage that they can refer to machines on the network by names that are usually easier to remember than the numerical network addresses. For system administrators, using a <code class="systemitem">DNS</code> server, also known as a <em class="firstterm">nameserver</em>, enables changing the <code class="systemitem">IP</code> address for a host without ever affecting the name-based queries. The use of the <code class="systemitem">DNS</code> databases is not only for resolving <code class="systemitem">IP</code> addresses to domain names and their use is becoming broader and broader as DNSSEC is deployed.
+ </div><div class="section" id="sec-Introduction_to_DNS"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.1. Introduction to DNS</h2></div></div></div><a id="idm225489672016" class="indexterm"></a><div class="para">
+ <code class="systemitem">DNS</code> is usually implemented using one or more centralized servers that are authoritative for certain domains. When a client host requests information from a nameserver, it usually connects to port 53. The nameserver then attempts to resolve the name requested. If the nameserver is configured to be a recursive name servers and it does not have an authoritative answer, or does not already have the answer cached from an earlier query, it queries other nameservers, called <em class="firstterm">root nameservers</em>, to determine which nameservers are authoritative for the name in question, and then queries them to get the requested name. Nameservers configured as purely authoritative, with recursion disabled, will not do lookups on behalf of clients.
+ </div><div class="section" id="sec-dns-introduction-zones"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.1.1. Nameserver Zones</h3></div></div></div><a id="idm225489676416" class="indexterm"></a><a id="idm225489678480" class="indexterm"></a><div class="para">
+ In a <code class="systemitem">DNS</code> server, all information is stored in basic data elements called <em class="firstterm">resource records</em> (<acronym class="acronym">RR</acronym>). Resource records are defined in <a href="http://www.rfc-editor.org/rfc/rfc1034.txt">RFC 1034</a>. The domain names are organized into a tree structure. Each level of the hierarchy is divided by a period (<code class="literal">.</code>). For example: The root domain, denoted by <code class="literal">.</code>, is the root of the <code class="systemitem">DNS</code> tree, which is at level zero. The domain name <code class="systemitem">com</code>, referred to as the <em class="firstterm">top-level domain</em> (<acronym class="acronym">TLD</acronym>) is a child of the root domain (<code class="literal">.</code>) so it is the first level of the hierarchy. The domain name <code class="systemitem">example.com</code> is at the second level of the hierarchy.
+ </div><div class="example" id="example-dns-introduction-zones-rr"><h6>Example 10.1. A Simple Resource Record</h6><div class="example-contents"><div class="para">
+ An example of a simple <em class="firstterm">resource record</em> (<acronym class="acronym">RR</acronym>):
+ </div><pre class="screen">example.com. 86400 IN A 192.0.2.1</pre><div class="para">
+ The domain name, <code class="systemitem">example.com</code>, is the <em class="firstterm">owner</em> for the RR. The value <code class="literal">86400</code> is the <em class="firstterm">time to live</em> (<acronym class="acronym">TTL</acronym>). The letters <code class="literal">IN</code>, meaning <span class="quote">“<span class="quote">the Internet system</span>”</span>, indicate the <em class="firstterm">class</em> of the RR. The letter <code class="literal">A</code> indicates the <em class="firstterm">type</em> of RR (in this example, a host address). The host address <code class="systemitem">192.0.2.1</code> is the data contained in the final section of this RR. This one line example is a RR. A set of RRs with the same type, owner, and class is called a <em class="firstterm">resource record set</em> (<acronym class="acronym">RRSet</acronym>).
+ </div></div></div><br class="example-break" /><a id="idm225455637760" class="indexterm"></a><a id="idm225455640160" class="indexterm"></a><a id="idm225455641840" class="indexterm"></a><div class="para">
+ Zones are defined on authoritative nameservers through the use of <em class="firstterm">zone files</em>, which contain definitions of the resource records in each zone. Zone files are stored on <em class="firstterm">primary nameservers</em> (also called <em class="firstterm">master nameservers</em>), where changes are made to the files, and <em class="firstterm">secondary nameservers</em> (also called <em class="firstterm">slave nameservers</em>), which receive zone definitions from the primary nameservers. Both primary and secondary nameservers are authoritative for the zone and look the same to clients. Depending on the configuration, any nameserver can also serve as a primary or secondary server for multiple zones at the same time.
+ </div><div class="para">
+ Note that administrators of <code class="systemitem">DNS</code> and <code class="systemitem">DHCP</code> servers, as well as any provisioning applications, should agree on the host name format used in an organization. See <a class="xref" href="ch-Configure_Host_Names.html#sec-Recommended_Naming_Practices">Section 3.1.1, “Recommended Naming Practices”</a> for more information on the format of host names.
+ </div></div><div class="section" id="sec-dns-introduction-nameservers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.1.2. Nameserver Types</h3></div></div></div><div class="para">
+ There are two nameserver configuration types:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225441199200" class="indexterm"></a>
+ <a id="idm225441202032" class="indexterm"></a>
+ <a id="idm225441203776" class="indexterm"></a>
+ <a id="idm225441205920" class="indexterm"></a>
+ <a id="idm225441209696" class="indexterm"></a>
+ <a id="idm225441209536" class="indexterm"></a>
+ authoritative </span></dt><dd><div class="para">
+ Authoritative nameservers answer to resource records that are part of their zones only. This category includes both primary (master) and secondary (slave) nameservers.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225441212944" class="indexterm"></a>
+ <a id="idm225441215424" class="indexterm"></a>
+ recursive </span></dt><dd><div class="para">
+ Recursive nameservers offer resolution services, but they are not authoritative for any zone. Answers for all resolutions are cached in a memory for a fixed period of time, which is specified by the retrieved resource record.
+ </div></dd></dl></div><div class="para">
+ Although a nameserver can be both authoritative and recursive at the same time, it is recommended not to combine the configuration types. To be able to perform their work, authoritative servers should be available to all clients all the time. On the other hand, since the recursive lookup takes far more time than authoritative responses, recursive servers should be available to a restricted number of clients only, otherwise they are prone to distributed denial of service (DDoS) attacks.
+ </div></div><div class="section" id="sec-dns-introduction-bind"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.1.3. BIND as a Nameserver</h3></div></div></div><a id="idm225485867648" class="indexterm"></a><a id="idm225485869760" class="indexterm"></a><a id="idm225485872112" class="indexterm"></a><a id="idm225485874832" class="indexterm"></a><a id="idm225485876352" class="indexterm"></a><a id="idm225485878272" class="indexterm"></a><div class="para">
+ BIND consists of a set of DNS-related programs. It contains a nameserver called <code class="systemitem">named</code>, an administration utility called <code class="command">rndc</code>, and a debugging tool called <code class="command">dig</code>. See <em class="citetitle">Fedora 20 System Administrator's Guide</em> for more information on how to run a service in Fedora.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-dhcp-additional-resources.html"><strong>Prev</strong>9.6. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-BIND.html"><strong>Next</strong>10.2. BIND</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Introduction_to_Fedora_Networking.html b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Introduction_to_Fedora_Networking.html
new file mode 100644
index 0000000..09584d6
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/ch-Introduction_to_Fedora_Networking.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 1. Introduction to Fedora Networking</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="part-Networking.html" title="Part I. Networking" /><link rel="prev" href="part-Networking.html" title="Part I. Networking" /><link rel="next" href="sec-Introduction_to_NetworkManager.html" title="1.2. Introduction to NetworkManager" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Networking.html"><strong>Prev</strong></a></li><li class="next"><a accesskey=
"n" href="sec-Introduction_to_NetworkManager.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-Introduction_to_Fedora_Networking" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 1. Introduction to Fedora Networking</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Introduction_to_Fedora_Networking.html#sec-How_this_Book_is_Structured">1.1. How this Book is Structured</a></span></dt><dt><span class="section"><a href="sec-Introduction_to_NetworkManager.html">1.2. Introduction to NetworkManager</a></span></dt><dt><span class="section"><a href="sec-Installing_NetworkManager.html">1.3. Installing NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Installing_NetworkManager.html#sec-The_NetworkManager_Daemon">1.3.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="sec-Interacting_with_NetworkManager.html">1.3.2. Interacting wi
th NetworkManager</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Network_Config_Using_CLI.html">1.4. Network Configuration Using the Command Line Interface (CLI)</a></span></dt><dt><span class="section"><a href="sec-Network_Config_Using_nmcli.html">1.5. Network Configuration Using NetworkManager's CLI (nmcli)</a></span></dt><dt><span class="section"><a href="sec-NetworkManager_and_the_Network_Scripts.html">1.6. NetworkManager and the Network Scripts</a></span></dt><dt><span class="section"><a href="sec-Network_Configuration_Using_sysconfig_Files.html">1.7. Network Configuration Using sysconfig Files</a></span></dt><dt><span class="section"><a href="sec-Introduction_to_Fedora_Networking-additional_resources.html">1.8. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Introduction_to_Fedora_Networking-additional_resources.html#sec-Introduction_to_Fedora_Networking-docs-inst">1.8.1. Installed Documentation</a></span></dt></dl></
dd></dl></div><div class="section" id="sec-How_this_Book_is_Structured"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.1. How this Book is Structured</h2></div></div></div><div class="para">
+ All new material in this book has been written and arranged in such a way as to clearly separate introductory material, such as explanations of concepts and use cases, from configuration tasks. The authors hope that you can quickly find configuration instructions you need, while still providing some relevant explanations and conceptual material to help you understand and decide on the appropriate tasks relevant to your needs. Where material has been reused from the <a href="https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/index.html"><em class="citetitle">Red Hat Enterprise Linux 6 Deployment Guide</em></a>, it has been reviewed and changed, where possible, to fit this idea of separating concepts from tasks.
+ </div><div class="para">
+ The material is grouped according to the goal rather than the method. Instructions on how to achieve a specific task using different methods are grouped together. This is intended to make it easier for you to find the information on how to achieve a particular task or goal, and at the same time allow you to quickly see the different methods available.
+ </div><div class="para">
+ In each chapter, the configuration methods will be presented in the following order: A graphical user interface (GUI) method, such as the use of <span class="application"><strong>nm-connection-editor</strong></span> or <span class="application"><strong>control-network</strong></span> to direct <code class="systemitem">NetworkManager</code>, then <span class="application"><strong>NetworkManager</strong></span>'s command-line tool <span class="application"><strong>nmcli</strong></span>, and then finally methods using the command line and configuration files. The command line can be used to issue commands and to compose or edit configuration files, therefore the use of the <span class="application"><strong>ip</strong></span> commands and configuration files will be documented together.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Networking.html"><strong>Prev</strong>Part I. Networking</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Introduction_to_NetworkManager.html"><strong>Next</strong>1.2. Introduction to NetworkManager</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/ch09s02s03.html b/public_html/en-US/Fedora/21/html/Networking_Guide/ch09s02s03.html
new file mode 100644
index 0000000..898c59f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/ch09s02s03.html
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.2.3. Starting and Stopping the Server</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-dhcp-configuring-server.html" title="9.2. Configuring a DHCP Server" /><link rel="prev" href="lease-database.html" title="9.2.2. Lease Database" /><link rel="next" href="dhcp-relay-agent.html" title="9.3. DHCP Relay Agent" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="lease-database.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href=
"dhcp-relay-agent.html"><strong>Next</strong></a></li></ul><div class="section" id="idm225427813824"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225427813824">9.2.3. Starting and Stopping the Server</h3></div></div></div><a id="idm225427813056" class="indexterm"></a><a id="idm225427811616" class="indexterm"></a><a id="idm225427810176" class="indexterm"></a><a id="idm225427808576" class="indexterm"></a><div class="important"><div class="admonition_header"><h2>Starting the DHCP Server for the First Time</h2></div><div class="admonition"><div class="para">
+ When the <code class="systemitem">DHCP</code> server is started for the first time, it fails unless the <code class="filename">dhcpd.leases</code> file exists. You can use the command <code class="command">touch /var/lib/dhcpd/dhcpd.leases</code> to create the file if it does not exist. If the same server is also running BIND as a <code class="systemitem">DNS</code> server, this step is not necessary, as starting the <code class="command">named</code> service automatically checks for a <code class="filename">dhcpd.leases</code> file.
+ </div><div class="para">
+ Do not create a new lease file on a system that was previously running. If you do, all old leases are lost which causes many problems. The correct solution is to rename the <code class="filename">dhcpd.leases~</code> backup file to <code class="filename">dhcpd.leases</code> and then start the daemon.
+ </div></div></div><div class="para">
+ To start the <code class="systemitem">DHCP</code> service, use the following command:
+ </div><pre class="screen"><code class="command">systemctl start dhcpd.service</code></pre><div class="para">
+ To stop the <code class="systemitem">DHCP</code> server, type:
+ </div><pre class="screen"><code class="command">systemctl stop dhcpd.service</code></pre><div class="para">
+ By default, the <code class="systemitem">DHCP</code> service does not start at boot time. To configure the daemon to start automatically at boot time, run:
+ </div><pre class="screen"><code class="command">systemctl enable dhcpd.service</code></pre><div class="para">
+
+ </div><a id="idm225453059568" class="indexterm"></a><a id="idm225453058128" class="indexterm"></a><div class="para">
+ If more than one network interface is attached to the system, but the <code class="systemitem">DHCP</code> server should only listen for <code class="systemitem">DHCP</code> requests on one of the interfaces, configure the <code class="systemitem">DHCP</code> server to listen only on that device. The <code class="systemitem">DHCP</code> daemon will only listen on interfaces for which it finds a subnet declaration in the <code class="filename">/etc/dhcp/dhcpd.conf</code> file.
+ </div><div class="para">
+ This is useful for a firewall machine with two network cards. One network card can be configured as a <code class="systemitem">DHCP</code> client to retrieve an <code class="systemitem">IP</code> address to the Internet. The other network card can be used as a <code class="systemitem">DHCP</code> server for the internal network behind the firewall. Specifying only the network card connected to the internal network makes the system more secure because users can not connect to the daemon via the Internet.
+ </div><div class="para">
+ To specify command-line options, copy and then edit the <code class="filename">dhcpd.service</code> file as the <code class="systemitem">root</code> user. For example, as follows:
+<pre class="screen">~]# <code class="command">cp /usr/lib/systemd/system/dhcpd.service /etc/systemd/system/</code>
+~]# <code class="command">vi /etc/systemd/system/dhcpd.service</code></pre>
+ Edit the line under section [Service]: <pre class="synopsis">ExecStart=/usr/sbin/dhcpd -f -cf /etc/dhcp/dhcpd.conf -user dhcpd -group dhcpd --no-pid <em class="replaceable"><code>your_interface_name(s)</code></em></pre> Then, as the <code class="systemitem">root</code> user, restart the service:
+<pre class="screen">~]# <code class="command">systemctl --system daemon-reload</code>
+~]# <code class="command">systemctl restart dhcpd</code></pre>
+
+ </div><div class="para">
+ Command line options can be appended to <code class="command">ExecStart=/usr/sbin/dhcpd</code> in the <code class="filename">/etc/systemd/system/dhcpd.service</code> unit file under section [Service]. They include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-p <em class="replaceable"><code>portnum</code></em></code> — Specifies the UDP port number on which <code class="command">dhcpd</code> should listen. The default is port 67. The <code class="systemitem">DHCP</code> server transmits responses to the <code class="systemitem">DHCP</code> clients at a port number one greater than the UDP port specified. For example, if the default port 67 is used, the server listens on port 67 for requests and responds to the client on port 68. If a port is specified here and the <code class="systemitem">DHCP</code> relay agent is used, the same port on which the <code class="systemitem">DHCP</code> relay agent should listen must be specified. See <a class="xref" href="dhcp-relay-agent.html">Section 9.3, “DHCP Relay Agent”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-f</code> — Runs the daemon as a foreground process. This is mostly used for debugging.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-d</code> — Logs the <code class="systemitem">DHCP</code> server daemon to the standard error descriptor. This is mostly used for debugging. If this is not specified, the log is written to <code class="filename">/var/log/messages</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-cf <em class="replaceable"><code>filename</code></em> </code> — Specifies the location of the configuration file. The default location is <code class="filename">/etc/dhcp/dhcpd.conf</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-lf <em class="replaceable"><code>filename</code></em> </code> — Specifies the location of the lease database file. If a lease database file already exists, it is very important that the same file be used every time the <code class="systemitem">DHCP</code> server is started. It is strongly recommended that this option only be used for debugging purposes on non-production machines. The default location is <code class="filename">/var/lib/dhcpd/dhcpd.leases</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-q</code> — Do not print the entire copyright message when starting the daemon.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="lease-database.html"><strong>Prev</strong>9.2.2. Lease Database</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="dhcp-relay-agent.html"><strong>Next</strong>9.3. DHCP Relay Agent</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/dhcp-relay-agent.html b/public_html/en-US/Fedora/21/html/Networking_Guide/dhcp-relay-agent.html
new file mode 100644
index 0000000..f44f5cd
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/dhcp-relay-agent.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.3. DHCP Relay Agent</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-DHCP_Servers.html" title="Chapter 9. DHCP Servers" /><link rel="prev" href="ch09s02s03.html" title="9.2.3. Starting and Stopping the Server" /><link rel="next" href="sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent.html" title="9.3.2. Configure dhcrelay as a DHCPv6 relay agent" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s02s03.html"><strong>Prev</stron
g></a></li><li class="next"><a accesskey="n" href="sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent.html"><strong>Next</strong></a></li></ul><div class="section" id="dhcp-relay-agent"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.3. DHCP Relay Agent</h2></div></div></div><a id="idm225481258576" class="indexterm"></a><a id="idm225481257136" class="indexterm"></a><a id="idm225481255696" class="indexterm"></a><div class="para">
+ The DHCP Relay Agent (<span class="application"><strong>dhcrelay</strong></span>) enables the relay of <code class="systemitem">DHCP</code> and <code class="systemitem">BOOTP</code> requests from a subnet with no <code class="systemitem">DHCP</code> server on it to one or more <code class="systemitem">DHCP</code> servers on other subnets.
+ </div><div class="para">
+ When a <code class="systemitem">DHCP</code> client requests information, the DHCP Relay Agent forwards the request to the list of <code class="systemitem">DHCP</code> servers specified when the DHCP Relay Agent is started. When a <code class="systemitem">DHCP</code> server returns a reply, the reply is broadcast or unicast on the network that sent the original request.
+ </div><div class="para">
+ The DHCP Relay Agent for <code class="systemitem">IPv4</code>, <span class="application"><strong>dhcrelay</strong></span>, listens for <code class="systemitem">DHCPv4</code> and <code class="systemitem">BOOTP</code> requests on all interfaces unless the interfaces are specified in <code class="filename">/etc/sysconfig/dhcrelay</code> with the <code class="computeroutput">INTERFACES</code> directive. See <a class="xref" href="sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent.html">Section 9.3.2, “Configure dhcrelay as a DHCPv6 relay agent”</a>. The DHCP Relay Agent for <code class="systemitem">IPv6</code>, <span class="application"><strong>dhcrelay6</strong></span>, does not have this default behavior and interfaces to listen for <code class="systemitem">DHCPv6</code> requests must be specified. See <a class="xref" href="sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent.html">Section 9.3.2, “Configure dhcrelay as a DHCPv6 relay agent”</a>.
+ </div><div class="para">
+ <span class="application"><strong>dhcrelay</strong></span> can either be run as a <code class="systemitem">DHCPv4</code> and <code class="systemitem">BOOTP</code> relay agent (by default) or as a <code class="systemitem">DHCPv6</code> relay agent (with <code class="option">-6</code> argument). To see the usage message, issue the command <code class="command">dhcrelay -h</code>.
+ </div><div class="section" id="sec-Configure_dhcrelay_as_a_DHCPv4_and_BOOTP_relay_agent"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.3.1. Configure dhcrelay as a DHCPv4 and BOOTP relay agent</h3></div></div></div><div class="para">
+ To run <span class="application"><strong>dhcrelay</strong></span> in <code class="systemitem">DHCPv4</code> and <code class="systemitem">BOOTP</code> mode specify the servers to which the requests should be forwarded to. Copy and then edit the <code class="filename">dhcrelay.service</code> file as the <code class="systemitem">root</code> user:
+<pre class="screen">~]# <code class="command">cp /lib/systemd/system/dhcrelay.service /etc/systemd/system/</code>
+~]# <code class="command">vi /etc/systemd/system/dhcrelay.service</code></pre>
+ </div><div class="para">
+ Edit the <code class="option">ExecStart</code> option under section [Service] and add one or more server <code class="systemitem">IPv4</code> addresses to the end of the line, for example: <pre class="synopsis">ExecStart=/usr/sbin/dhcrelay -d --no-pid 192.168.1.1</pre>
+ </div><div class="para">
+ If you also want to specify interfaces where the DHCP Relay Agent listens for <code class="systemitem">DHCP</code> requests, add them to the <code class="option">ExecStart</code> option with <code class="option">-i</code> argument (otherwise it will listen on all interfaces), for example: <pre class="synopsis">ExecStart=/usr/sbin/dhcrelay -d --no-pid 192.168.1.1 -i em1</pre> For other options see the <code class="filename">dhcrelay(8)</code> man page.
+ </div><div class="para">
+ To activate the changes made, as the <code class="systemitem">root</code> user, restart the service:
+<pre class="screen">~]# <code class="command">systemctl --system daemon-reload</code>
+~]# <code class="command">systemctl restart dhcrelay</code></pre>
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch09s02s03.html"><strong>Prev</strong>9.2.3. Starting and Stopping the Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent.html"><strong>Next</strong>9.3.2. Configure dhcrelay as a DHCPv6 relay agent</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/images/Editing-Bridge-Connection-1_Gnome3.png b/public_html/en-US/Fedora/21/html/Networking_Guide/images/Editing-Bridge-Connection-1_Gnome3.png
new file mode 100644
index 0000000..77b5101
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/images/Editing-Bridge-Connection-1_Gnome3.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/images/Network-Details-Wired_Gnome3.png b/public_html/en-US/Fedora/21/html/Networking_Guide/images/Network-Details-Wired_Gnome3.png
new file mode 100644
index 0000000..ba58a95
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/images/Network-Details-Wired_Gnome3.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/images/Network-Wired_Gnome3.png b/public_html/en-US/Fedora/21/html/Networking_Guide/images/Network-Wired_Gnome3.png
new file mode 100644
index 0000000..56fca9c
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/Networking_Guide/images/Network-Wired_Gnome3.png differ
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/index.html b/public_html/en-US/Fedora/21/html/Networking_Guide/index.html
new file mode 100644
index 0000000..467f180
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/index.html
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Networking Guide</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><meta name="description" content="The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guid
e to form the foundation for this book." /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="next" href="pr01.html" title="Preface" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pr01.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="book" id="idm225480464432" lang="en-US"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"
><span class="productname">Fedora</span> <span class="productnumber">21</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="idm225480464432" class="title">Networking Guide</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">Configuration and Administration of networking for Fedora 20</h2></div><p class="edition">Edition 2</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+ <span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> </object></span>
+
+ </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="en-US" class="authorgroup" lang="en-US"><div class="author"><h3 class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:swadeley at redhat.com">swadeley at redhat.com</a></code></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="idm225417530832" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2014 Red Hat, Inc. and others.
+ </div><div class="para">
+ The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
+ </div><div class="para">
+ Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
+ </div><div class="para">
+ Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
+ </div><div class="para">
+ For guidelines on the permitted uses of the Fedora trademarks, refer to <a href="https://fedoraproject.org/wiki/Legal:Trademark_guidelines">https://fedoraproject.org/wiki/Legal:Trademark_guidelines</a>.
+ </div><div class="para">
+ <span class="trademark">Linux</span>® is the registered trademark of Linus Torvalds in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Java</span>® is a registered trademark of Oracle and/or its affiliates.
+ </div><div class="para">
+ <span class="trademark">XFS</span>® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
+ </div><div class="para">
+ <span class="trademark">MySQL</span>® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
+ </div><div class="para">
+ All other trademarks are the property of their respective owners.
+ </div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract"><h6>Abstract</h6><div class="para">
+ The <em class="citetitle">Networking Guide</em> documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking.
+ </div><div class="para">
+ This book is based on the <em class="citetitle">Deployment Guide</em> from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.
+ </div></div></div></div><hr /></div><div class="toc"><dl class="toc"><dt><span class="preface"><a href="pr01.html">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="pr01.html#sec-Preface-Target_Audience">1. Target Audience</a></span></dt><dt><span class="section"><a href="sec-Preface-About_this_book.html">2. About This Book</a></span></dt><dt><span class="section"><a href="sec-Whats-New.html">3. What's new in Fedora 20</a></span></dt><dt><span class="section"><a href="sec-Preface-Book_Organization.html">4. How to Read this Book</a></span></dt><dt><span class="section"><a href="pr01s05.html">5. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="pr01s05.html#idm225443496592">5.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="pr01s05s02.html">5.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="pr01s05s03.html">5.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="sect
ion"><a href="sec-Preface-Feedback.html">6. Feedback</a></span></dt><dt><span class="section"><a href="pref-Acknowledgments.html">7. Acknowledgments</a></span></dt></dl></dd><dt><span class="part"><a href="part-Networking.html">I. Networking</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-Introduction_to_Fedora_Networking.html">1. Introduction to Fedora Networking</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Introduction_to_Fedora_Networking.html#sec-How_this_Book_is_Structured">1.1. How this Book is Structured</a></span></dt><dt><span class="section"><a href="sec-Introduction_to_NetworkManager.html">1.2. Introduction to NetworkManager</a></span></dt><dt><span class="section"><a href="sec-Installing_NetworkManager.html">1.3. Installing NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Installing_NetworkManager.html#sec-The_NetworkManager_Daemon">1.3.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><
a href="sec-Interacting_with_NetworkManager.html">1.3.2. Interacting with NetworkManager</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Network_Config_Using_CLI.html">1.4. Network Configuration Using the Command Line Interface (CLI)</a></span></dt><dt><span class="section"><a href="sec-Network_Config_Using_nmcli.html">1.5. Network Configuration Using NetworkManager's CLI (nmcli)</a></span></dt><dt><span class="section"><a href="sec-NetworkManager_and_the_Network_Scripts.html">1.6. NetworkManager and the Network Scripts</a></span></dt><dt><span class="section"><a href="sec-Network_Configuration_Using_sysconfig_Files.html">1.7. Network Configuration Using sysconfig Files</a></span></dt><dt><span class="section"><a href="sec-Introduction_to_Fedora_Networking-additional_resources.html">1.8. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Introduction_to_Fedora_Networking-additional_resources.html#sec-Introduction_to_Fedora_Netw
orking-docs-inst">1.8.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configure_Networking.html">2. Configure Networking</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Networking.html#sec-Static_and_Dynamic_Interface_Settings">2.1. Static and Dynamic Interface Settings</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Networking.html#sec-When_to_Use_Static_Network_Interface_Settings">2.1.1. When to Use Static Network Interface Settings</a></span></dt><dt><span class="section"><a href="ch-Configure_Networking.html#sec-When_to_Use_Dynamic_Interface_Settings">2.1.2. When to Use Dynamic Interface Settings</a></span></dt><dt><span class="section"><a href="ch-Configure_Networking.html#sec-Selecting_Network_Configuration_Methods">2.1.3. Selecting Network Configuration Methods</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_NetworkManager_with_the_GNOME_Graphical_Us
er_Interface.html">2.2. Using NetworkManager with the GNOME Graphical User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html#sec-Connecting_to_a_Network_Using_a_GUI">2.2.1. Connecting to a Network Using a GUI</a></span></dt><dt><span class="section"><a href="sec-Configuring_New_and_Editing_Existing_Connections.html">2.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="sec-Connecting_to_a_Network_Automatically.html">2.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="sec-System-wide_and_Private_Connection_Profiles.html">2.2.4. System-wide and Private Connection Profiles</a></span></dt><dt><span class="section"><a href="sec-Configuring_a_Wired_Ethernet_Connection.html">2.2.5. Configuring a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="sec-Configuring_a_Wi-Fi_Connec
tion.html">2.2.6. Configuring a Wi-Fi Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_VPN_Connection.html">2.2.7. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_Mobile_Broadband_Connection.html">2.2.8. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_DSL_Connection.html">2.2.9. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="sec-Configuring_Connection_Settings.html">2.2.10. Configuring Connection Settings</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_the_Command_Line_Interface.html">2.3. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_the_Command_Line_Interface.html#sec-Configuring_a_Network_Interface_Using_ifcg_Files">2.3.1. Configuring a Network Interface Using ifcfg Files</a></span></dt><dt><span class="section"><a
href="sec-Configuring_a_Network_Interface_Using_ip_commands.html">2.3.2. Configuring a Network Interface Using ip Commands</a></span></dt><dt><span class="section"><a href="sec-Static-Routes_and_the_Default_Gateway.html">2.3.3. Static Routes and the Default Gateway</a></span></dt><dt><span class="section"><a href="sec-Configuring_Static_Routes_in_ifcfg_files.html">2.3.4. Configuring Static Routes in ifcfg files</a></span></dt><dt><span class="section"><a href="sec-Configuring_IPv6_Tokenized_Interface_Identifiers.html">2.3.5. Configuring IPv6 Tokenized Interface Identifiers</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html">2.4. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html#sec-Understanding_the_nmcli_Options">2.4.1. Understanding the nmcli Options</a></span></dt><dt><span class="section"><
a href="sec-Connecting_to_a_Network_Using_nmcli.html">2.4.2. Connecting to a Network Using nmcli</a></span></dt><dt><span class="section"><a href="sec-Configuring_Static_Routes_Using_nmcli.html">2.4.3. Configuring Static Routes Using nmcli</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_Networking-additional_resources.html">2.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_Networking-additional_resources.html#sec-Configure_Networking-docs-inst">2.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-Configure_Networking_Online_Documentation.html">2.5.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configure_Host_Names.html">3. Configure Host Names</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Host_Names.html#sec_Understanding_Host_Names">3.1. Understanding Host Names</a></span></dt><dd><dl><dt><span c
lass="section"><a href="ch-Configure_Host_Names.html#sec-Recommended_Naming_Practices">3.1.1. Recommended Naming Practices</a></span></dt></dl></dd><dt><span class="section"><a href="sec_Configuring_Host_Names_Using_hostnamectl.html">3.2. Configuring Host Names Using hostnamectl</a></span></dt><dd><dl><dt><span class="section"><a href="sec_Configuring_Host_Names_Using_hostnamectl.html#sec_View_All_the_Host_Names">3.2.1. View All the Host Names</a></span></dt><dt><span class="section"><a href="sec_Set_All_the_Host_Names.html">3.2.2. Set All the Host Names</a></span></dt><dt><span class="section"><a href="sec_Set_a_Particular_Host_Name.html">3.2.3. Set a Particular Host Name</a></span></dt><dt><span class="section"><a href="sec_Clear_a_Particular_Host_Name.html">3.2.4. Clear a Particular Host Name</a></span></dt><dt><span class="section"><a href="sec_Changing_Host_Names_Remotely.html">3.2.5. Changing Host Names Remotely</a></span></dt></dl></dd><dt><span class="section"><a hre
f="sec-Configuring_Host_Names_Using_nmcli.html">3.3. Configuring Host Names Using nmcli</a></span></dt><dt><span class="section"><a href="sec-additional_resources.html">3.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-additional_resources.html#sec-hostnamectl-docs-inst">3.4.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-hostnamectl-Online_Documentation.html">3.4.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configure_Network_Bonding.html">4. Configure Network Bonding</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Network_Bonding.html#sec-Bond-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces">4.1. Understanding the Default Behavior of Master and Slave Interfaces</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Bond_Connection_Using_a_GUI.html">4.2. Creating a Bond Connection Using a GUI</a></span><
/dt><dd><dl><dt><span class="section"><a href="sec-Creating_a_Bond_Connection_Using_a_GUI.html#sec-Establishing_a_Bond_Connection">4.2.1. Establishing a Bond Connection</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Network_Bonding_Using_the_Command_Line_Interface.html">4.3. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Network_Bonding_Using_the_Command_Line_Interface.html#sec-Check_if_Bonding_Kernel_Module_is_Installed">4.3.1. Check if Bonding Kernel Module is Installed</a></span></dt><dt><span class="section"><a href="sec-Create_a_Channel_Bonding_Interface.html">4.3.2. Create a Channel Bonding Interface</a></span></dt><dt><span class="section"><a href="sec-Creating_SLAVE_Interfaces.html">4.3.3. Creating SLAVE Interfaces</a></span></dt><dt><span class="section"><a href="sec-Activating_a_Channel_Bond.html">4.3.4. Activating a Channel Bond</a></span></dt><dt><span class="section"><a href="sec-Creating_Mul
tiple_Bonds.html">4.3.5. Creating Multiple Bonds</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_Channel_Bonding.html">4.4. Using Channel Bonding</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_Channel_Bonding.html#s3-modules-bonding-directives">4.4.1. Bonding Module Directives</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli.html">4.5. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="sec-Configure_Network_Bonding-additional_resources.html">4.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_Network_Bonding-additional_resources.html#sec-Configure_Network_Bonding-docs-inst">4.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-Configure_Network_Bonding_Online_Documentation.html">4.6.2. Online Documentation</a></span></dt></dl></dd
></dl></dd><dt><span class="chapter"><a href="ch-Configure_Network_Teaming.html">5. Configure Network Teaming</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Network_Teaming.html#sec-Understanding_Network_Teaming">5.1. Understanding Network Teaming</a></span></dt><dt><span class="section"><a href="sec-Comparison_of_Network_Teaming_to_Bonding.html">5.2. Comparison of Network Teaming to Bonding</a></span></dt><dt><span class="section"><a href="sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces.html">5.3. Understanding the Default Behavior of Master and Slave Interfaces</a></span></dt><dt><span class="section"><a href="sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners.html">5.4. Understanding the Network Teaming Daemon and the "Runners"</a></span></dt><dt><span class="section"><a href="sec-Install_the_Network_Teaming_Daemon.html">5.5. Install the Network Teaming Daemon</a></span></dt><dt><span class="section"><a href="se
c-Converting_a_Bond_to_a_Team.html">5.6. Converting a Bond to a Team</a></span></dt><dt><span class="section"><a href="sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team.html">5.7. Selecting Interfaces to Use as Ports for a Network Team</a></span></dt><dt><span class="section"><a href="sec-Selecting_Network_Team_Configuration_Methods.html">5.8. Selecting Network Team Configuration Methods</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Network_Team_Using_a_GUI.html">5.9. Creating a Network Team Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Creating_a_Network_Team_Using_a_GUI.html#sec-Establishing_a_Team_Connection">5.9.1. Establishing a Team Connection</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_a_Network_Team_Using-the_Command_Line.html">5.10. Configure a Network Team Using the Command Line</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_a_Network_Team_Using-the_Comman
d_Line.html#sec-Creating_a_Network_Team_Using_teamd">5.10.1. Creating a Network Team Using teamd</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Network_Team_Using_ifcfg_Files.html">5.10.2. Creating a Network Team Using ifcfg Files</a></span></dt><dt><span class="section"><a href="sec-Add_a_port_to_a_Network_Team_Using_iputils.html">5.10.3. Add a Port to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="sec-Listing_the_ports_of_a_Team_Using_teamnl.html">5.10.4. Listing the ports of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="sec-Configuring_Options_of_a_Team_Using_teamnl.html">5.10.5. Configuring Options of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="sec-Add_an_address_to_a_Network_Team_Using_iputils.html">5.10.6. Add an Address to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils.html">5.10.7
. Bring up an Interface to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl.html">5.10.8. Viewing the Active Port Options of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl.html">5.10.9. Setting the Active Port Options of a Team Using teamnl</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Controlling_teamd_with_teamdctl.html">5.11. Controlling teamd with teamdctl</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Controlling_teamd_with_teamdctl.html#sec-Add_a_port_to_a_Network_Team">5.11.1. Add a Port to a Network Team</a></span></dt><dt><span class="section"><a href="sec-Remove_a_Port_From_a_Network_Team.html">5.11.2. Remove a Port From a Network Team</a></span></dt><dt><span class="section"><a href="sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team.html">5.11.3. Apply a Configuration to a
Port in a Network Team</a></span></dt><dt><span class="section"><a href="sec-View_the_Configuration_of_a_Port_in_a_Network_Team.html">5.11.4. View the Configuration of a Port in a Network Team</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_teamd_Runners.html">5.12. Configure teamd Runners</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_teamd_Runners.html#sec-Configure_the_broadcast_Runner">5.12.1. Configure the broadcast Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_the_random_Runner.html">5.12.2. Configure the random Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_the_roundrobin_Runner.html">5.12.3. Configure the roundrobin Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_the_activebackup_Runner.html">5.12.4. Configure the activebackup Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_the_loadbalance_Runner.html">5.12.5. Configure the
loadbalance Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_the_LACP_Runner.html">5.12.6. Configure the LACP (802.3ad) Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_Monitoring_of_the_Link_State.html">5.12.7. Configure Monitoring of the Link State</a></span></dt><dt><span class="section"><a href="sec-Configure_Port_Selection_Override.html">5.12.8. Configure Port Selection Override</a></span></dt><dt><span class="section"><a href="sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm.html">5.12.9. Configure BPF-based Tx Port Selectors</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_Network_Teaming_Using_nmcli.html">5.13. Configure Network Teaming Using nmcli</a></span></dt><dt><span class="section"><a href="sec-Network_Teaming-additional_resources.html">5.14. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Network_Teaming-additional_resources.html#se
c-teamd-docs-inst">5.14.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-teamd_docs-online.html">5.14.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configure_Network_Bridging.html">6. Configure Network Bridging</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Network_Bridging.html#sec-Configure_Network_Bridging_Using_a_GUI">6.1. Configure Network Bridging Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Network_Bridging.html#sec-Establishing_a_Bridge_Connection">6.1.1. Establishing a Bridge Connection</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Network_Bridging_Using_the_Command_Line_Interface.html">6.2. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Network_Bridging_Using_the_Command_Line_Interface.html#sec-Check_if_Bridging_Kernel_Module_is_Installed">6.2.1. Check
if Bridging Kernel Module is Installed</a></span></dt><dt><span class="section"><a href="sec-Create_a_Network_Bridge.html">6.2.2. Create a Network Bridge</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html">6.3. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="sec-Network_Bridging-additional_resources.html">6.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Network_Bridging-additional_resources.html#sec-Network_Bridging-docs-inst">6.4.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configure_802_1Q_VLAN_Tagging.html">7. Configure 802.1Q VLAN tagging</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_802_1Q_VLAN_Tagging.html#sec-Selecting_VLAN_Interface_Configuration_Methods">7.1. Selecting VLAN Interface Configuration Methods</a></
span></dt><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html">7.2. Configure 802.1Q VLAN Tagging Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html#sec-Establishing_a_VLAN_Connection">7.2.1. Establishing a VLAN Connection</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html">7.3. Configure 802.1Q VLAN Tagging Using the Command Line</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html#sec-Setting_Up_802.1Q_VLAN_Tagging_Using_ifcfg_Files">7.3.1. Setting Up 802.1Q VLAN Tagging Using ifcfg Files</a></span></dt><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_ip_Commands.html">7.3.2. Configure 802.1Q VLAN Tagging Using ip Commands</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_
Using_the_Command_Line_Tool_nmcli.html">7.4. Configure 802.1Q VLAN Tagging Using the Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging-additional_resources.html">7.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging-additional_resources.html#sec-Configure_802_1Q_VLAN_Tagging-docs-inst">7.5.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Consistent_Network_Device_Naming.html">8. Consistent Network Device Naming</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Consistent_Network_Device_Naming.html#sec-Naming_Schemes_Hierarchy">8.1. Naming Schemes Hierarchy</a></span></dt><dt><span class="section"><a href="sec-Understanding_the_Device_Renaming_Procedure.html">8.2. Understanding the Device Renaming Procedure</a></span></dt><dt><span class="section"><a href="sec-Understanding_the_Predictable_Netw
ork_Interface_Device_Names.html">8.3. Understanding the Predictable Network Interface Device Names</a></span></dt><dt><span class="section"><a href="sec-Naming_Scheme_for_Network_Devices_Available_for_Linux_on_System_z.html">8.4. Naming Scheme for Network Devices Available for Linux on System z</a></span></dt><dt><span class="section"><a href="sec-Naming_Scheme_for_VLAN_Interfaces.html">8.5. Naming Scheme for VLAN Interfaces</a></span></dt><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming_Using_biosdevname.html">8.6. Consistent Network Device Naming Using biosdevname</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming_Using_biosdevname.html#sec-Consistent_Network_Device_Naming-System_Requirements">8.6.1. System Requirements</a></span></dt><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming-Enabling_and_Disabling.html">8.6.2. Enabling and Disabling the Feature</a></span></dt></dl></dd><dt><sp
an class="section"><a href="sec-Consistent_Network_Device_Naming-Notes.html">8.7. Notes for Administrators</a></span></dt><dt><span class="section"><a href="sec-Controlling_the_Selection_of_Network_Device_Names.html">8.8. Controlling the Selection of Network Device Names</a></span></dt><dt><span class="section"><a href="sec-Disabling_Consistent_Network_Device_Naming.html">8.9. Disabling Consistent Network Device Naming</a></span></dt><dt><span class="section"><a href="sec_Troubleshooting_Network_Device_Naming.html">8.10. Troubleshooting Network Device Naming</a></span></dt><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming-additional_resources.html">8.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming-additional_resources.html#sec-Consistent_Network_Device_Naming-docs-inst">8.11.1. Installed Documentation</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="part-
Servers.html">II. Servers</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-DHCP_Servers.html">9. DHCP Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-DHCP_Servers.html#sec-dhcp-why">9.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="sec-dhcp-configuring-server.html">9.2. Configuring a DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="sec-dhcp-configuring-server.html#config-file">9.2.1. Configuration File</a></span></dt><dt><span class="section"><a href="lease-database.html">9.2.2. Lease Database</a></span></dt><dt><span class="section"><a href="ch09s02s03.html">9.2.3. Starting and Stopping the Server</a></span></dt></dl></dd><dt><span class="section"><a href="dhcp-relay-agent.html">9.3. DHCP Relay Agent</a></span></dt><dd><dl><dt><span class="section"><a href="dhcp-relay-agent.html#sec-Configure_dhcrelay_as_a_DHCPv4_and_BOOTP_relay_agent">9.3.1. Configure dhcrelay as a DHCPv4 and BOOTP relay agent</a></sp
an></dt><dt><span class="section"><a href="sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent.html">9.3.2. Configure dhcrelay as a DHCPv6 relay agent</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_a_Multihomed_DHCP_Server.html">9.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configuring_a_Multihomed_DHCP_Server.html#sec-dns_Host_Configuration">9.4.1. Host Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="sec-dhcp_for_ipv6_dhcpv6.html">9.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="sec-dhcp-additional-resources.html">9.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-dhcp-additional-resources.html#sec-dhcp-installed-docs">9.6.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-DNS_Servers.html">10. DNS Servers</a></span></dt><dd><dl><dt><span class="section">
<a href="ch-DNS_Servers.html#sec-Introduction_to_DNS">10.1. Introduction to DNS</a></span></dt><dd><dl><dt><span class="section"><a href="ch-DNS_Servers.html#sec-dns-introduction-zones">10.1.1. Nameserver Zones</a></span></dt><dt><span class="section"><a href="ch-DNS_Servers.html#sec-dns-introduction-nameservers">10.1.2. Nameserver Types</a></span></dt><dt><span class="section"><a href="ch-DNS_Servers.html#sec-dns-introduction-bind">10.1.3. BIND as a Nameserver</a></span></dt></dl></dd><dt><span class="section"><a href="sec-BIND.html">10.2. BIND</a></span></dt><dd><dl><dt><span class="section"><a href="sec-BIND.html#sec-bind-empty-zones">10.2.1. Empty Zones</a></span></dt><dt><span class="section"><a href="sec-bind-namedconf.html">10.2.2. Configuring the named Service</a></span></dt><dt><span class="section"><a href="sec-bind-zone.html">10.2.3. Editing Zone Files</a></span></dt><dt><span class="section"><a href="sec-bind-rndc.html">10.2.4. Using the rndc Utility</a></span></
dt><dt><span class="section"><a href="sec-bind-dig.html">10.2.5. Using the dig Utility</a></span></dt><dt><span class="section"><a href="sec-bind-features.html">10.2.6. Advanced Features of BIND</a></span></dt><dt><span class="section"><a href="sec-bind-mistakes.html">10.2.7. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="sec-bind-additional-resources.html">10.2.8. Additional Resources</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="appendix"><a href="app-Revision_History.html">A. Revision History</a></span></dt><dt><span class="index"><a href="ix01.html">Index</a></span></dt></dl></div></div><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pr01.html"><strong>Next</strong>Preface</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/ix01.html b/public_html/en-US/Fedora/21/html/Networking_Guide/ix01.html
new file mode 100644
index 0000000..dfaaf14
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/ix01.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Index</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="index.html" title="Networking Guide" /><link rel="prev" href="app-Revision_History.html" title="Appendix A. Revision History" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="app-Revision_History.html"><strong>Prev</strong></a></li><li class="next"></li></ul><div class="index" id="idm225428861104"><div class="titlepage"><div><div><h1 class="title">Index</h1></div><
/div></div><div class="index"><div class="indexdiv"><h3>Symbols</h3><dl><dt>/etc/named.conf (see BIND)</dt><dt> /etc/sysconfig/dhcpd , <a class="indexterm" href="ch09s02s03.html">Starting and Stopping the Server</a></dt></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>authoritative nameserver (see BIND)</dt></dl></div><div class="indexdiv"><h3>B</h3><dl><dt>Berkeley Internet Name Domain (see BIND)</dt><dt>BIND</dt><dd><dl><dt>additional resources</dt><dd><dl><dt>installed documentation, <a class="indexterm" href="sec-bind-additional-resources.html#sec-bind-installed-docs">Installed Documentation</a></dt><dt>related books, <a class="indexterm" href="sec-bind-additional-resources.html#sec-bind-related-books">Related Books</a></dt><dt>useful websites, <a class="indexterm" href="sec-bind-additional-resources.html#sec-bind-useful-websites">Useful Websites</a></dt></dl></dd><dt>common mistakes, <a class="indexterm" href="sec-bind-mistakes.html">Common Mistakes to Avoid</a></dt><
dt>configuration</dt><dd><dl><dt>acl statement, <a class="indexterm" href="sec-bind-namedconf.html#sec-bind-namedconf-state">Common Statement Types</a></dt><dt>comment tags, <a class="indexterm" href="sec-bind-namedconf.html#sec-bind-namedconf-comm">Comment Tags</a></dt><dt>controls statement, <a class="indexterm" href="sec-bind-namedconf.html#sec-bind-namedconf-state-other">Other Statement Types</a></dt><dt>include statement, <a class="indexterm" href="sec-bind-namedconf.html#sec-bind-namedconf-state">Common Statement Types</a></dt><dt>key statement, <a class="indexterm" href="sec-bind-namedconf.html#sec-bind-namedconf-state-other">Other Statement Types</a></dt><dt>logging statement, <a class="indexterm" href="sec-bind-namedconf.html#sec-bind-namedconf-state-other">Other Statement Types</a></dt><dt>options statement, <a class="indexterm" href="sec-bind-namedconf.html#sec-bind-namedconf-state">Common Statement Types</a></dt><dt>server statement, <a class="indexterm" href="se
c-bind-namedconf.html#sec-bind-namedconf-state-other">Other Statement Types</a></dt><dt>trusted-keys statement, <a class="indexterm" href="sec-bind-namedconf.html#sec-bind-namedconf-state-other">Other Statement Types</a></dt><dt>view statement, <a class="indexterm" href="sec-bind-namedconf.html#sec-bind-namedconf-state-other">Other Statement Types</a></dt><dt>zone statement, <a class="indexterm" href="sec-bind-namedconf.html#sec-bind-namedconf-state">Common Statement Types</a></dt></dl></dd><dt>directories</dt><dd><dl><dt>/etc/named/, <a class="indexterm" href="sec-bind-namedconf.html">Configuring the named Service</a></dt><dt>/var/named/, <a class="indexterm" href="sec-bind-zone.html">Editing Zone Files</a></dt><dt>/var/named/data/, <a class="indexterm" href="sec-bind-zone.html">Editing Zone Files</a></dt><dt>/var/named/dynamic/, <a class="indexterm" href="sec-bind-zone.html">Editing Zone Files</a></dt><dt>/var/named/slaves/, <a class="indexterm" href="sec-bind-zone.html">E
diting Zone Files</a></dt></dl></dd><dt>features</dt><dd><dl><dt>Automatic Zone Transfer (AXFR), <a class="indexterm" href="sec-bind-features.html#sec-bind-features-ixfr">Incremental Zone Transfers (IXFR)</a></dt><dt>DNS Security Extensions (DNSSEC), <a class="indexterm" href="sec-bind-features.html#sec-bind-features-dnssec">DNS Security Extensions (DNSSEC)</a></dt><dt>Incremental Zone Transfer (IXFR), <a class="indexterm" href="sec-bind-features.html#sec-bind-features-ixfr">Incremental Zone Transfers (IXFR)</a></dt><dt>Internet Protocol version 6 (IPv6), <a class="indexterm" href="sec-bind-features.html#sec-bind-features-ipv6">Internet Protocol version 6 (IPv6)</a></dt><dt>multiple views, <a class="indexterm" href="sec-bind-features.html#sec-bind-features-views">Multiple Views</a></dt><dt>Transaction SIGnature (TSIG), <a class="indexterm" href="sec-bind-features.html#sec-bind-features-tsig">Transaction SIGnatures (TSIG)</a></dt></dl></dd><dt>files</dt><dd><dl><dt>/etc/named
.conf, <a class="indexterm" href="sec-bind-namedconf.html">Configuring the named Service</a>, <a class="indexterm" href="sec-bind-rndc.html#sec-bind-rndc-configuration">Configuring the Utility</a></dt><dt>/etc/rndc.conf, <a class="indexterm" href="sec-bind-rndc.html#sec-bind-rndc-configuration">Configuring the Utility</a></dt><dt>/etc/rndc.key, <a class="indexterm" href="sec-bind-rndc.html#sec-bind-rndc-configuration">Configuring the Utility</a></dt></dl></dd><dt>resource record, <a class="indexterm" href="ch-DNS_Servers.html#sec-dns-introduction-zones">Nameserver Zones</a></dt><dt>types</dt><dd><dl><dt>authoritative nameserver, <a class="indexterm" href="ch-DNS_Servers.html#sec-dns-introduction-nameservers">Nameserver Types</a></dt><dt>primary (master) nameserver, <a class="indexterm" href="ch-DNS_Servers.html#sec-dns-introduction-zones">Nameserver Zones</a>, <a class="indexterm" href="ch-DNS_Servers.html#sec-dns-introduction-nameservers">Nameserver Types</a></dt><dt>recurs
ive nameserver, <a class="indexterm" href="ch-DNS_Servers.html#sec-dns-introduction-nameservers">Nameserver Types</a></dt><dt>secondary (slave) nameserver, <a class="indexterm" href="ch-DNS_Servers.html#sec-dns-introduction-zones">Nameserver Zones</a>, <a class="indexterm" href="ch-DNS_Servers.html#sec-dns-introduction-nameservers">Nameserver Types</a></dt></dl></dd><dt>utilities</dt><dd><dl><dt>dig, <a class="indexterm" href="ch-DNS_Servers.html#sec-dns-introduction-bind">BIND as a Nameserver</a>, <a class="indexterm" href="sec-bind-dig.html">Using the dig Utility</a>, <a class="indexterm" href="sec-bind-features.html#sec-bind-features-dnssec">DNS Security Extensions (DNSSEC)</a></dt><dt>named, <a class="indexterm" href="ch-DNS_Servers.html#sec-dns-introduction-bind">BIND as a Nameserver</a>, <a class="indexterm" href="sec-bind-namedconf.html">Configuring the named Service</a></dt><dt>rndc, <a class="indexterm" href="ch-DNS_Servers.html#sec-dns-introduction-bind">BIND as a
Nameserver</a>, <a class="indexterm" href="sec-bind-rndc.html">Using the rndc Utility</a></dt></dl></dd><dt>zones</dt><dd><dl><dt>$INCLUDE directive, <a class="indexterm" href="sec-bind-zone.html#sec-bind-zone-directives">Common Directives</a></dt><dt>$ORIGIN directive, <a class="indexterm" href="sec-bind-zone.html#sec-bind-zone-directives">Common Directives</a></dt><dt>$TTL directive, <a class="indexterm" href="sec-bind-zone.html#sec-bind-zone-directives">Common Directives</a></dt><dt>A (Address) resource record, <a class="indexterm" href="sec-bind-zone.html#sec-bind-zone-rr">Common Resource Records</a></dt><dt>CNAME (Canonical Name) resource record, <a class="indexterm" href="sec-bind-zone.html#sec-bind-zone-rr">Common Resource Records</a></dt><dt>comment tags, <a class="indexterm" href="sec-bind-zone.html#sec-bind-zone-comm">Comment Tags</a></dt><dt>description, <a class="indexterm" href="ch-DNS_Servers.html#sec-dns-introduction-zones">Nameserver Zones</a></dt><dt>example
usage, <a class="indexterm" href="sec-bind-zone.html#sec-bind-zone-examples-basic">A Simple Zone File</a>, <a class="indexterm" href="sec-bind-zone.html#sec-bind-configuration-zone-reverse">A Reverse Name Resolution Zone File</a></dt><dt>MX (Mail Exchange) resource record, <a class="indexterm" href="sec-bind-zone.html#sec-bind-zone-rr">Common Resource Records</a></dt><dt>NS (Nameserver) resource record, <a class="indexterm" href="sec-bind-zone.html#sec-bind-zone-rr">Common Resource Records</a></dt><dt>PTR (Pointer) resource record, <a class="indexterm" href="sec-bind-zone.html#sec-bind-zone-rr">Common Resource Records</a></dt><dt>SOA (Start of Authority) resource record, <a class="indexterm" href="sec-bind-zone.html#sec-bind-zone-rr">Common Resource Records</a></dt></dl></dd></dl></dd><dt>bonding (see channel bonding)</dt></dl></div><div class="indexdiv"><h3>C</h3><dl><dt>channel bonding</dt><dd><dl><dt>configuration, <a class="indexterm" href="sec-Using_Channel_Bonding.htm
l">Using Channel Bonding</a></dt><dt>description, <a class="indexterm" href="sec-Using_Channel_Bonding.html">Using Channel Bonding</a></dt><dt>parameters to bonded interfaces, <a class="indexterm" href="sec-Using_Channel_Bonding.html#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>channel bonding interface (see kernel module)</dt></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>default gateway, <a class="indexterm" href="sec-Static-Routes_and_the_Default_Gateway.html">Static Routes and the Default Gateway</a></dt><dt>DHCP, <a class="indexterm" href="ch-DHCP_Servers.html">DHCP Servers</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="sec-dhcp-additional-resources.html">Additional Resources</a></dt><dt>command-line options, <a class="indexterm" href="ch09s02s03.html">Starting and Stopping the Server</a></dt><dt>dhcpd.conf, <a class="indexterm" href="sec-dhcp-configuring-server.html#config-file">Configuration File</a></dt><dt>
dhcpd.leases, <a class="indexterm" href="ch09s02s03.html">Starting and Stopping the Server</a></dt><dt>dhcpd6.conf, <a class="indexterm" href="sec-dhcp_for_ipv6_dhcpv6.html">DHCP for IPv6 (DHCPv6)</a></dt><dt>DHCPv6, <a class="indexterm" href="sec-dhcp_for_ipv6_dhcpv6.html">DHCP for IPv6 (DHCPv6)</a></dt><dt>dhcrelay, <a class="indexterm" href="dhcp-relay-agent.html">DHCP Relay Agent</a></dt><dt>global parameters, <a class="indexterm" href="sec-dhcp-configuring-server.html#config-file">Configuration File</a></dt><dt>group, <a class="indexterm" href="sec-dhcp-configuring-server.html#config-file">Configuration File</a></dt><dt>options, <a class="indexterm" href="sec-dhcp-configuring-server.html#config-file">Configuration File</a></dt><dt>reasons for using, <a class="indexterm" href="ch-DHCP_Servers.html#sec-dhcp-why">Why Use DHCP?</a></dt><dt>Relay Agent, <a class="indexterm" href="dhcp-relay-agent.html">DHCP Relay Agent</a></dt><dt>server configuration, <a class="indexterm" h
ref="sec-dhcp-configuring-server.html">Configuring a DHCP Server</a></dt><dt>shared-network, <a class="indexterm" href="sec-dhcp-configuring-server.html#config-file">Configuration File</a></dt><dt>starting the server, <a class="indexterm" href="ch09s02s03.html">Starting and Stopping the Server</a></dt><dt>stopping the server, <a class="indexterm" href="ch09s02s03.html">Starting and Stopping the Server</a></dt><dt>subnet, <a class="indexterm" href="sec-dhcp-configuring-server.html#config-file">Configuration File</a></dt></dl></dd><dt>dhcpd.conf, <a class="indexterm" href="sec-dhcp-configuring-server.html#config-file">Configuration File</a></dt><dt>dhcpd.leases, <a class="indexterm" href="ch09s02s03.html">Starting and Stopping the Server</a></dt><dt>dhcrelay, <a class="indexterm" href="dhcp-relay-agent.html">DHCP Relay Agent</a></dt><dt>dig (see BIND)</dt><dt>DNS</dt><dd><dl><dt>definition, <a class="indexterm" href="ch-DNS_Servers.html">DNS Servers</a></dt><dd><dl><dt>(see al
so BIND)</dt></dl></dd></dl></dd><dt>Dynamic Host Configuration Protocol (see DHCP)</dt></dl></div><div class="indexdiv"><h3>F</h3><dl><dt>feedback</dt><dd><dl><dt>contact information for this manual, <a class="indexterm" href="sec-Preface-Feedback.html">Feedback</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>K</h3><dl><dt>kernel module</dt><dd><dl><dt>bonding module, <a class="indexterm" href="sec-Using_Channel_Bonding.html">Using Channel Bonding</a></dt><dd><dl><dt>description, <a class="indexterm" href="sec-Using_Channel_Bonding.html">Using Channel Bonding</a></dt><dt>parameters to bonded interfaces, <a class="indexterm" href="sec-Using_Channel_Bonding.html#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>module parameters</dt><dd><dl><dt>bonding module parameters, <a class="indexterm" href="sec-Using_Channel_Bonding.html#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd></dl></dd></dl></div><div class="indexd
iv"><h3>M</h3><dl><dt>Multihomed DHCP</dt><dd><dl><dt>host configuration, <a class="indexterm" href="sec-Configuring_a_Multihomed_DHCP_Server.html#sec-dns_Host_Configuration">Host Configuration</a></dt><dt>server configuration, <a class="indexterm" href="sec-Configuring_a_Multihomed_DHCP_Server.html">Configuring a Multihomed DHCP Server</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>N</h3><dl><dt>named (see BIND)</dt><dt>nameserver (see DNS)</dt><dt>NIC</dt><dd><dl><dt>binding into single channel, <a class="indexterm" href="sec-Using_Channel_Bonding.html">Using Channel Bonding</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>primary nameserver (see BIND)</dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>recursive nameserver (see BIND)</dt><dt>resource record (see BIND)</dt><dt>rndc (see BIND)</dt><dt>root nameserver (see BIND)</dt></dl></div><div class="indexdiv"><h3>S</h3><dl><dt>secondary nameserver (see BIND)</dt><dt>static route, <a class
="indexterm" href="sec-Static-Routes_and_the_Default_Gateway.html">Static Routes and the Default Gateway</a></dt></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="app-Revision_History.html"><strong>Prev</strong>Appendix A. Revision History</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/lease-database.html b/public_html/en-US/Fedora/21/html/Networking_Guide/lease-database.html
new file mode 100644
index 0000000..a584fc8
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/lease-database.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.2.2. Lease Database</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-dhcp-configuring-server.html" title="9.2. Configuring a DHCP Server" /><link rel="prev" href="sec-dhcp-configuring-server.html" title="9.2. Configuring a DHCP Server" /><link rel="next" href="ch09s02s03.html" title="9.2.3. Starting and Stopping the Server" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-dhcp-configuring-server.html"><strong>Prev</strong><
/a></li><li class="next"><a accesskey="n" href="ch09s02s03.html"><strong>Next</strong></a></li></ul><div class="section" id="lease-database"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.2. Lease Database</h3></div></div></div><div class="para">
+ On the <code class="systemitem">DHCP</code> server, the file <code class="filename">/var/lib/dhcpd/dhcpd.leases</code> stores the <code class="systemitem">DHCP</code> client lease database. Do not change this file. <code class="systemitem">DHCP</code> lease information for each recently assigned <code class="systemitem">IP</code> address is automatically stored in the lease database. The information includes the length of the lease, to whom the <code class="systemitem">IP</code> address has been assigned, the start and end dates for the lease, and the MAC address of the network interface card that was used to retrieve the lease.
+ </div><div class="para">
+ All times in the lease database are in Coordinated Universal Time (UTC), not local time.
+ </div><div class="para">
+ The lease database is recreated from time to time so that it is not too large. First, all known leases are saved in a temporary lease database. The <code class="filename">dhcpd.leases</code> file is renamed <code class="filename">dhcpd.leases~</code> and the temporary lease database is written to <code class="filename">dhcpd.leases</code>.
+ </div><div class="para">
+ The <code class="systemitem">DHCP</code> daemon could be killed or the system could crash after the lease database has been renamed to the backup file but before the new file has been written. If this happens, the <code class="filename">dhcpd.leases</code> file does not exist, but it is required to start the service. Do not create a new lease file. If you do, all old leases are lost which causes many problems. The correct solution is to rename the <code class="filename">dhcpd.leases~</code> backup file to <code class="filename">dhcpd.leases</code> and then start the daemon.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-dhcp-configuring-server.html"><strong>Prev</strong>9.2. Configuring a DHCP Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch09s02s03.html"><strong>Next</strong>9.2.3. Starting and Stopping the Server</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/part-Networking.html b/public_html/en-US/Fedora/21/html/Networking_Guide/part-Networking.html
new file mode 100644
index 0000000..3fcf148
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/part-Networking.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Part I. Networking</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="index.html" title="Networking Guide" /><link rel="prev" href="pref-Acknowledgments.html" title="7. Acknowledgments" /><link rel="next" href="ch-Introduction_to_Fedora_Networking.html" title="Chapter 1. Introduction to Fedora Networking" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Acknowledgments.html"><strong>Prev</strong></a></li><li class="next"><a acc
esskey="n" href="ch-Introduction_to_Fedora_Networking.html"><strong>Next</strong></a></li></ul><div class="part" id="part-Networking"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part I. Networking</h1></div></div></div><div class="partintro" id="idm225484356016"><div></div><div class="para">
+ This part describes how to configure the network on Fedora.
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="ch-Introduction_to_Fedora_Networking.html">1. Introduction to Fedora Networking</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Introduction_to_Fedora_Networking.html#sec-How_this_Book_is_Structured">1.1. How this Book is Structured</a></span></dt><dt><span class="section"><a href="sec-Introduction_to_NetworkManager.html">1.2. Introduction to NetworkManager</a></span></dt><dt><span class="section"><a href="sec-Installing_NetworkManager.html">1.3. Installing NetworkManager</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Installing_NetworkManager.html#sec-The_NetworkManager_Daemon">1.3.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="sec-Interacting_with_NetworkManager.html">1.3.2. Interacting with NetworkManager</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Network_Config_Using_CLI.html
">1.4. Network Configuration Using the Command Line Interface (CLI)</a></span></dt><dt><span class="section"><a href="sec-Network_Config_Using_nmcli.html">1.5. Network Configuration Using NetworkManager's CLI (nmcli)</a></span></dt><dt><span class="section"><a href="sec-NetworkManager_and_the_Network_Scripts.html">1.6. NetworkManager and the Network Scripts</a></span></dt><dt><span class="section"><a href="sec-Network_Configuration_Using_sysconfig_Files.html">1.7. Network Configuration Using sysconfig Files</a></span></dt><dt><span class="section"><a href="sec-Introduction_to_Fedora_Networking-additional_resources.html">1.8. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Introduction_to_Fedora_Networking-additional_resources.html#sec-Introduction_to_Fedora_Networking-docs-inst">1.8.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configure_Networking.html">2. Configure Networking</a></span
></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Networking.html#sec-Static_and_Dynamic_Interface_Settings">2.1. Static and Dynamic Interface Settings</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Networking.html#sec-When_to_Use_Static_Network_Interface_Settings">2.1.1. When to Use Static Network Interface Settings</a></span></dt><dt><span class="section"><a href="ch-Configure_Networking.html#sec-When_to_Use_Dynamic_Interface_Settings">2.1.2. When to Use Dynamic Interface Settings</a></span></dt><dt><span class="section"><a href="ch-Configure_Networking.html#sec-Selecting_Network_Configuration_Methods">2.1.3. Selecting Network Configuration Methods</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html">2.2. Using NetworkManager with the GNOME Graphical User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_NetworkManager_with_the_GNOME
_Graphical_User_Interface.html#sec-Connecting_to_a_Network_Using_a_GUI">2.2.1. Connecting to a Network Using a GUI</a></span></dt><dt><span class="section"><a href="sec-Configuring_New_and_Editing_Existing_Connections.html">2.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="sec-Connecting_to_a_Network_Automatically.html">2.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="sec-System-wide_and_Private_Connection_Profiles.html">2.2.4. System-wide and Private Connection Profiles</a></span></dt><dt><span class="section"><a href="sec-Configuring_a_Wired_Ethernet_Connection.html">2.2.5. Configuring a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="sec-Configuring_a_Wi-Fi_Connection.html">2.2.6. Configuring a Wi-Fi Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_VPN_Connection.html">2.2.7. Establishing a VPN Connection</a></s
pan></dt><dt><span class="section"><a href="sec-Establishing_a_Mobile_Broadband_Connection.html">2.2.8. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_DSL_Connection.html">2.2.9. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="sec-Configuring_Connection_Settings.html">2.2.10. Configuring Connection Settings</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_the_Command_Line_Interface.html">2.3. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_the_Command_Line_Interface.html#sec-Configuring_a_Network_Interface_Using_ifcg_Files">2.3.1. Configuring a Network Interface Using ifcfg Files</a></span></dt><dt><span class="section"><a href="sec-Configuring_a_Network_Interface_Using_ip_commands.html">2.3.2. Configuring a Network Interface Using ip Commands</a></span></dt><dt><span class="section"><a href="sec-Stat
ic-Routes_and_the_Default_Gateway.html">2.3.3. Static Routes and the Default Gateway</a></span></dt><dt><span class="section"><a href="sec-Configuring_Static_Routes_in_ifcfg_files.html">2.3.4. Configuring Static Routes in ifcfg files</a></span></dt><dt><span class="section"><a href="sec-Configuring_IPv6_Tokenized_Interface_Identifiers.html">2.3.5. Configuring IPv6 Tokenized Interface Identifiers</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html">2.4. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html#sec-Understanding_the_nmcli_Options">2.4.1. Understanding the nmcli Options</a></span></dt><dt><span class="section"><a href="sec-Connecting_to_a_Network_Using_nmcli.html">2.4.2. Connecting to a Network Using nmcli</a></span></dt><dt><span class="section"><a href="sec-Configuring_Static_Routes_Using
_nmcli.html">2.4.3. Configuring Static Routes Using nmcli</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_Networking-additional_resources.html">2.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_Networking-additional_resources.html#sec-Configure_Networking-docs-inst">2.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-Configure_Networking_Online_Documentation.html">2.5.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configure_Host_Names.html">3. Configure Host Names</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Host_Names.html#sec_Understanding_Host_Names">3.1. Understanding Host Names</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Host_Names.html#sec-Recommended_Naming_Practices">3.1.1. Recommended Naming Practices</a></span></dt></dl></dd><dt><span class="section"><a href=
"sec_Configuring_Host_Names_Using_hostnamectl.html">3.2. Configuring Host Names Using hostnamectl</a></span></dt><dd><dl><dt><span class="section"><a href="sec_Configuring_Host_Names_Using_hostnamectl.html#sec_View_All_the_Host_Names">3.2.1. View All the Host Names</a></span></dt><dt><span class="section"><a href="sec_Set_All_the_Host_Names.html">3.2.2. Set All the Host Names</a></span></dt><dt><span class="section"><a href="sec_Set_a_Particular_Host_Name.html">3.2.3. Set a Particular Host Name</a></span></dt><dt><span class="section"><a href="sec_Clear_a_Particular_Host_Name.html">3.2.4. Clear a Particular Host Name</a></span></dt><dt><span class="section"><a href="sec_Changing_Host_Names_Remotely.html">3.2.5. Changing Host Names Remotely</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Host_Names_Using_nmcli.html">3.3. Configuring Host Names Using nmcli</a></span></dt><dt><span class="section"><a href="sec-additional_resources.html">3.4. Addition
al Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-additional_resources.html#sec-hostnamectl-docs-inst">3.4.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-hostnamectl-Online_Documentation.html">3.4.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configure_Network_Bonding.html">4. Configure Network Bonding</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Network_Bonding.html#sec-Bond-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces">4.1. Understanding the Default Behavior of Master and Slave Interfaces</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Bond_Connection_Using_a_GUI.html">4.2. Creating a Bond Connection Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Creating_a_Bond_Connection_Using_a_GUI.html#sec-Establishing_a_Bond_Connection">4.2.1. Establishing a Bond Connection</a></span></d
t></dl></dd><dt><span class="section"><a href="sec-Network_Bonding_Using_the_Command_Line_Interface.html">4.3. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Network_Bonding_Using_the_Command_Line_Interface.html#sec-Check_if_Bonding_Kernel_Module_is_Installed">4.3.1. Check if Bonding Kernel Module is Installed</a></span></dt><dt><span class="section"><a href="sec-Create_a_Channel_Bonding_Interface.html">4.3.2. Create a Channel Bonding Interface</a></span></dt><dt><span class="section"><a href="sec-Creating_SLAVE_Interfaces.html">4.3.3. Creating SLAVE Interfaces</a></span></dt><dt><span class="section"><a href="sec-Activating_a_Channel_Bond.html">4.3.4. Activating a Channel Bond</a></span></dt><dt><span class="section"><a href="sec-Creating_Multiple_Bonds.html">4.3.5. Creating Multiple Bonds</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_Channel_Bonding.html">4.4. Using Channel Bonding</a></span></dt
><dd><dl><dt><span class="section"><a href="sec-Using_Channel_Bonding.html#s3-modules-bonding-directives">4.4.1. Bonding Module Directives</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli.html">4.5. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="sec-Configure_Network_Bonding-additional_resources.html">4.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_Network_Bonding-additional_resources.html#sec-Configure_Network_Bonding-docs-inst">4.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-Configure_Network_Bonding_Online_Documentation.html">4.6.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configure_Network_Teaming.html">5. Configure Network Teaming</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_N
etwork_Teaming.html#sec-Understanding_Network_Teaming">5.1. Understanding Network Teaming</a></span></dt><dt><span class="section"><a href="sec-Comparison_of_Network_Teaming_to_Bonding.html">5.2. Comparison of Network Teaming to Bonding</a></span></dt><dt><span class="section"><a href="sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces.html">5.3. Understanding the Default Behavior of Master and Slave Interfaces</a></span></dt><dt><span class="section"><a href="sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners.html">5.4. Understanding the Network Teaming Daemon and the "Runners"</a></span></dt><dt><span class="section"><a href="sec-Install_the_Network_Teaming_Daemon.html">5.5. Install the Network Teaming Daemon</a></span></dt><dt><span class="section"><a href="sec-Converting_a_Bond_to_a_Team.html">5.6. Converting a Bond to a Team</a></span></dt><dt><span class="section"><a href="sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team.html
">5.7. Selecting Interfaces to Use as Ports for a Network Team</a></span></dt><dt><span class="section"><a href="sec-Selecting_Network_Team_Configuration_Methods.html">5.8. Selecting Network Team Configuration Methods</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Network_Team_Using_a_GUI.html">5.9. Creating a Network Team Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Creating_a_Network_Team_Using_a_GUI.html#sec-Establishing_a_Team_Connection">5.9.1. Establishing a Team Connection</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_a_Network_Team_Using-the_Command_Line.html">5.10. Configure a Network Team Using the Command Line</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_a_Network_Team_Using-the_Command_Line.html#sec-Creating_a_Network_Team_Using_teamd">5.10.1. Creating a Network Team Using teamd</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Network_Team_Using_i
fcfg_Files.html">5.10.2. Creating a Network Team Using ifcfg Files</a></span></dt><dt><span class="section"><a href="sec-Add_a_port_to_a_Network_Team_Using_iputils.html">5.10.3. Add a Port to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="sec-Listing_the_ports_of_a_Team_Using_teamnl.html">5.10.4. Listing the ports of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="sec-Configuring_Options_of_a_Team_Using_teamnl.html">5.10.5. Configuring Options of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="sec-Add_an_address_to_a_Network_Team_Using_iputils.html">5.10.6. Add an Address to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils.html">5.10.7. Bring up an Interface to a Network Team Using iputils</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl.html">5.10.8. Viewing th
e Active Port Options of a Team Using teamnl</a></span></dt><dt><span class="section"><a href="sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl.html">5.10.9. Setting the Active Port Options of a Team Using teamnl</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Controlling_teamd_with_teamdctl.html">5.11. Controlling teamd with teamdctl</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Controlling_teamd_with_teamdctl.html#sec-Add_a_port_to_a_Network_Team">5.11.1. Add a Port to a Network Team</a></span></dt><dt><span class="section"><a href="sec-Remove_a_Port_From_a_Network_Team.html">5.11.2. Remove a Port From a Network Team</a></span></dt><dt><span class="section"><a href="sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team.html">5.11.3. Apply a Configuration to a Port in a Network Team</a></span></dt><dt><span class="section"><a href="sec-View_the_Configuration_of_a_Port_in_a_Network_Team.html">5.11.4. View the Configuration of a Port in a Ne
twork Team</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_teamd_Runners.html">5.12. Configure teamd Runners</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_teamd_Runners.html#sec-Configure_the_broadcast_Runner">5.12.1. Configure the broadcast Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_the_random_Runner.html">5.12.2. Configure the random Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_the_roundrobin_Runner.html">5.12.3. Configure the roundrobin Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_the_activebackup_Runner.html">5.12.4. Configure the activebackup Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_the_loadbalance_Runner.html">5.12.5. Configure the loadbalance Runner</a></span></dt><dt><span class="section"><a href="sec-Configure_the_LACP_Runner.html">5.12.6. Configure the LACP (802.3ad) Runner</a></span></dt><dt><span class="
section"><a href="sec-Configure_Monitoring_of_the_Link_State.html">5.12.7. Configure Monitoring of the Link State</a></span></dt><dt><span class="section"><a href="sec-Configure_Port_Selection_Override.html">5.12.8. Configure Port Selection Override</a></span></dt><dt><span class="section"><a href="sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm.html">5.12.9. Configure BPF-based Tx Port Selectors</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_Network_Teaming_Using_nmcli.html">5.13. Configure Network Teaming Using nmcli</a></span></dt><dt><span class="section"><a href="sec-Network_Teaming-additional_resources.html">5.14. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Network_Teaming-additional_resources.html#sec-teamd-docs-inst">5.14.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-teamd_docs-online.html">5.14.2. Online Documentation</a></span></dt></dl></dd
></dl></dd><dt><span class="chapter"><a href="ch-Configure_Network_Bridging.html">6. Configure Network Bridging</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Network_Bridging.html#sec-Configure_Network_Bridging_Using_a_GUI">6.1. Configure Network Bridging Using a GUI</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_Network_Bridging.html#sec-Establishing_a_Bridge_Connection">6.1.1. Establishing a Bridge Connection</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Network_Bridging_Using_the_Command_Line_Interface.html">6.2. Using the Command Line Interface (CLI)</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Network_Bridging_Using_the_Command_Line_Interface.html#sec-Check_if_Bridging_Kernel_Module_is_Installed">6.2.1. Check if Bridging Kernel Module is Installed</a></span></dt><dt><span class="section"><a href="sec-Create_a_Network_Bridge.html">6.2.2. Create a Network Bridge</a></span></dt></dl></dd><d
t><span class="section"><a href="sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html">6.3. Using the NetworkManager Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="sec-Network_Bridging-additional_resources.html">6.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Network_Bridging-additional_resources.html#sec-Network_Bridging-docs-inst">6.4.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configure_802_1Q_VLAN_Tagging.html">7. Configure 802.1Q VLAN tagging</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configure_802_1Q_VLAN_Tagging.html#sec-Selecting_VLAN_Interface_Configuration_Methods">7.1. Selecting VLAN Interface Configuration Methods</a></span></dt><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html">7.2. Configure 802.1Q VLAN Tagging Using a GUI</a></span></dt><dd><dl><dt><span class
="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html#sec-Establishing_a_VLAN_Connection">7.2.1. Establishing a VLAN Connection</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html">7.3. Configure 802.1Q VLAN Tagging Using the Command Line</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html#sec-Setting_Up_802.1Q_VLAN_Tagging_Using_ifcfg_Files">7.3.1. Setting Up 802.1Q VLAN Tagging Using ifcfg Files</a></span></dt><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_ip_Commands.html">7.3.2. Configure 802.1Q VLAN Tagging Using ip Commands</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli.html">7.4. Configure 802.1Q VLAN Tagging Using the Command Line Tool, nmcli</a></span></dt><dt><span class="section"><a href="sec-Configure_802_1Q_V
LAN_Tagging-additional_resources.html">7.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configure_802_1Q_VLAN_Tagging-additional_resources.html#sec-Configure_802_1Q_VLAN_Tagging-docs-inst">7.5.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Consistent_Network_Device_Naming.html">8. Consistent Network Device Naming</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Consistent_Network_Device_Naming.html#sec-Naming_Schemes_Hierarchy">8.1. Naming Schemes Hierarchy</a></span></dt><dt><span class="section"><a href="sec-Understanding_the_Device_Renaming_Procedure.html">8.2. Understanding the Device Renaming Procedure</a></span></dt><dt><span class="section"><a href="sec-Understanding_the_Predictable_Network_Interface_Device_Names.html">8.3. Understanding the Predictable Network Interface Device Names</a></span></dt><dt><span class="section"><a href="sec-Naming_Scheme_for_Network_Dev
ices_Available_for_Linux_on_System_z.html">8.4. Naming Scheme for Network Devices Available for Linux on System z</a></span></dt><dt><span class="section"><a href="sec-Naming_Scheme_for_VLAN_Interfaces.html">8.5. Naming Scheme for VLAN Interfaces</a></span></dt><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming_Using_biosdevname.html">8.6. Consistent Network Device Naming Using biosdevname</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming_Using_biosdevname.html#sec-Consistent_Network_Device_Naming-System_Requirements">8.6.1. System Requirements</a></span></dt><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming-Enabling_and_Disabling.html">8.6.2. Enabling and Disabling the Feature</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming-Notes.html">8.7. Notes for Administrators</a></span></dt><dt><span class="section"><a href="sec-Controlling_the_Selec
tion_of_Network_Device_Names.html">8.8. Controlling the Selection of Network Device Names</a></span></dt><dt><span class="section"><a href="sec-Disabling_Consistent_Network_Device_Naming.html">8.9. Disabling Consistent Network Device Naming</a></span></dt><dt><span class="section"><a href="sec_Troubleshooting_Network_Device_Naming.html">8.10. Troubleshooting Network Device Naming</a></span></dt><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming-additional_resources.html">8.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Consistent_Network_Device_Naming-additional_resources.html#sec-Consistent_Network_Device_Naming-docs-inst">8.11.1. Installed Documentation</a></span></dt></dl></dd></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Acknowledgments.html"><strong>Prev</strong>7. Acknowledgments</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></l
i><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Introduction_to_Fedora_Networking.html"><strong>Next</strong>Chapter 1. Introduction to Fedora Networking</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/part-Servers.html b/public_html/en-US/Fedora/21/html/Networking_Guide/part-Servers.html
new file mode 100644
index 0000000..57c2657
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/part-Servers.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Part II. Servers</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="index.html" title="Networking Guide" /><link rel="prev" href="sec-Consistent_Network_Device_Naming-additional_resources.html" title="8.11. Additional Resources" /><link rel="next" href="ch-DHCP_Servers.html" title="Chapter 9. DHCP Servers" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Consistent_Network_Device_Naming-additional_resources.html"><strong>Prev<
/strong></a></li><li class="next"><a accesskey="n" href="ch-DHCP_Servers.html"><strong>Next</strong></a></li></ul><div class="part" id="part-Servers"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part II. Servers</h1></div></div></div><div class="partintro" id="idm225428864912"><div></div><div class="para">
+ This part discusses how to set up servers normally required for networking.
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="ch-DHCP_Servers.html">9. DHCP Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-DHCP_Servers.html#sec-dhcp-why">9.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="sec-dhcp-configuring-server.html">9.2. Configuring a DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="sec-dhcp-configuring-server.html#config-file">9.2.1. Configuration File</a></span></dt><dt><span class="section"><a href="lease-database.html">9.2.2. Lease Database</a></span></dt><dt><span class="section"><a href="ch09s02s03.html">9.2.3. Starting and Stopping the Server</a></span></dt></dl></dd><dt><span class="section"><a href="dhcp-relay-agent.html">9.3. DHCP Relay Agent</a></span></dt><dd><dl><dt><span class="section"><a href="dhcp-relay-agent.html#sec-Configure_dhcrelay_as_a_DHCPv4_and_BOOTP_relay_agent">9.3.1. Configure dhcrelay as a DH
CPv4 and BOOTP relay agent</a></span></dt><dt><span class="section"><a href="sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent.html">9.3.2. Configure dhcrelay as a DHCPv6 relay agent</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_a_Multihomed_DHCP_Server.html">9.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configuring_a_Multihomed_DHCP_Server.html#sec-dns_Host_Configuration">9.4.1. Host Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="sec-dhcp_for_ipv6_dhcpv6.html">9.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="sec-dhcp-additional-resources.html">9.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-dhcp-additional-resources.html#sec-dhcp-installed-docs">9.6.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-DNS_Servers.html">10. DNS Servers</a></span></dt>
<dd><dl><dt><span class="section"><a href="ch-DNS_Servers.html#sec-Introduction_to_DNS">10.1. Introduction to DNS</a></span></dt><dd><dl><dt><span class="section"><a href="ch-DNS_Servers.html#sec-dns-introduction-zones">10.1.1. Nameserver Zones</a></span></dt><dt><span class="section"><a href="ch-DNS_Servers.html#sec-dns-introduction-nameservers">10.1.2. Nameserver Types</a></span></dt><dt><span class="section"><a href="ch-DNS_Servers.html#sec-dns-introduction-bind">10.1.3. BIND as a Nameserver</a></span></dt></dl></dd><dt><span class="section"><a href="sec-BIND.html">10.2. BIND</a></span></dt><dd><dl><dt><span class="section"><a href="sec-BIND.html#sec-bind-empty-zones">10.2.1. Empty Zones</a></span></dt><dt><span class="section"><a href="sec-bind-namedconf.html">10.2.2. Configuring the named Service</a></span></dt><dt><span class="section"><a href="sec-bind-zone.html">10.2.3. Editing Zone Files</a></span></dt><dt><span class="section"><a href="sec-bind-rndc.html">10.2.4. U
sing the rndc Utility</a></span></dt><dt><span class="section"><a href="sec-bind-dig.html">10.2.5. Using the dig Utility</a></span></dt><dt><span class="section"><a href="sec-bind-features.html">10.2.6. Advanced Features of BIND</a></span></dt><dt><span class="section"><a href="sec-bind-mistakes.html">10.2.7. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="sec-bind-additional-resources.html">10.2.8. Additional Resources</a></span></dt></dl></dd></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Consistent_Network_Device_Naming-additional_resources.html"><strong>Prev</strong>8.11. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-DHCP_Servers.html"><strong>Next</strong>Chapter 9. DHCP Servers</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/pr01.html b/public_html/en-US/Fedora/21/html/Networking_Guide/pr01.html
new file mode 100644
index 0000000..53861b3
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/pr01.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Preface</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="index.html" title="Networking Guide" /><link rel="prev" href="index.html" title="Networking Guide" /><link rel="next" href="sec-Preface-About_this_book.html" title="2. About This Book" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Preface-About_this_book.html"><strong>Next</stro
ng></a></li></ul><div xml:lang="en-US" class="preface" id="idm225487250336" lang="en-US"><div class="titlepage"><div><div><h1 id="idm225487250336" class="title">Preface</h1></div></div></div><div class="para">
+ The <em class="citetitle">Networking Guide</em> contains information on how to use the networking related features of Fedora 20.
+ </div><div class="para">
+ This manual discusses many intermediate topics such as the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Setting up a network (from establishing an Ethernet connection using <span class="application"><strong>NetworkManager</strong></span> to configuring channel bonding interfaces).
+ </div></li><li class="listitem"><div class="para">
+ Configuring <code class="systemitem">DHCP</code>, <span class="application"><strong>BIND</strong></span>, and <code class="systemitem">DNS</code>.
+ </div></li></ul></div><div class="section" id="sec-Preface-Target_Audience"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1. Target Audience</h2></div></div></div><div class="para">
+ The <em class="citetitle">Networking Guide</em> assumes you have a basic understanding of the Fedora operating system. If you need help with the installation of this system, see the <em class="citetitle">Fedora 20 Installation Guide</em>.
+ </div><div class="para">
+ This guide is not aimed exclusively at experienced Linux system administrators. The authors of this book have attempted to cater for a wider audience as more and more organizations and users become subscribers to Red Hat, Inc. At the same time we are aware of the need not to allow seemingly trivial information to get in the way of the tasks. Your feedback on how well we have met this goal is welcome.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Prev</strong>Networking Guide</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Preface-About_this_book.html"><strong>Next</strong>2. About This Book</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/pr01s05.html b/public_html/en-US/Fedora/21/html/Networking_Guide/pr01s05.html
new file mode 100644
index 0000000..2e91c5e
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/pr01s05.html
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5. Document Conventions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="pr01.html" title="Preface" /><link rel="prev" href="sec-Preface-Book_Organization.html" title="4. How to Read this Book" /><link rel="next" href="pr01s05s02.html" title="5.2. Pull-quote Conventions" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Preface-Book_Organization.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pr01s05s02.ht
ml"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="idm225451338832" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm225451338832">5. Document Conventions</h2></div></div></div><div class="para">
+ This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
+ </div><div class="para">
+ In PDF and paper editions, this manual uses typefaces drawn from the <a href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a> set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.
+ </div><div class="section" id="idm225443496592"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225443496592">5.1. Typographic Conventions</h3></div></div></div><div class="para">
+ Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
+ </div><div class="para">
+ <code class="literal">Mono-spaced Bold</code>
+ </div><div class="para">
+ Used to highlight system input, including shell commands, file names and paths. Also used to highlight keycaps and key combinations. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ To see the contents of the file <code class="filename">my_next_bestselling_novel</code> in your current working directory, enter the <code class="command">cat my_next_bestselling_novel</code> command at the shell prompt and press <span class="keycap"><strong>Enter</strong></span> to execute the command.
+ </div></blockquote></div><div class="para">
+ The above includes a file name, a shell command and a keycap, all presented in mono-spaced bold and all distinguishable thanks to context.
+ </div><div class="para">
+ Key combinations can be distinguished from keycaps by the hyphen connecting each part of a key combination. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to execute the command.
+ </div><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> to switch to the first virtual terminal. Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F1</strong></span> to return to your X-Windows session.
+ </div></blockquote></div><div class="para">
+ The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with each set pressed simultaneously).
+ </div><div class="para">
+ If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in <code class="literal">mono-spaced bold</code>. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ File-related classes include <code class="classname">filesystem</code> for file systems, <code class="classname">file</code> for files, and <code class="classname">dir</code> for directories. Each class has its own associated set of permissions.
+ </div></blockquote></div><div class="para">
+ <span class="application"><strong>Proportional Bold</strong></span>
+ </div><div class="para">
+ This denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ Choose <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Mouse</strong></span> from the main menu bar to launch <span class="application"><strong>Mouse Preferences</strong></span>. In the <span class="guilabel"><strong>Buttons</strong></span> tab, click the <span class="guilabel"><strong>Left-handed mouse</strong></span> check box and click <span class="guibutton"><strong>Close</strong></span> to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).
+ </div><div class="para">
+ To insert a special character into a <span class="application"><strong>gedit</strong></span> file, choose <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>Accessories</strong></span> → <span class="guimenuitem"><strong>Character Map</strong></span> from the main menu bar. Next, choose <span class="guimenu"><strong>Search</strong></span> → <span class="guimenuitem"><strong>Find…</strong></span> from the <span class="application"><strong>Character Map</strong></span> menu bar, type the name of the character in the <span class="guilabel"><strong>Search</strong></span> field and click <span class="guibutton"><strong>Next</strong></span>. The character you sought will be highlighted in the <span class="guilabel"><strong>Character Table</strong></span>. Double-click this highlighted character to place it in the <span class="guilabel"><strong>Text to copy</strong></span> field and then click the <span class="guibutton"><stron
g>Copy</strong></span> button. Now switch back to your document and choose <span class="guimenu"><strong>Edit</strong></span> → <span class="guimenuitem"><strong>Paste</strong></span> from the <span class="application"><strong>gedit</strong></span> menu bar.
+ </div></blockquote></div><div class="para">
+ The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context.
+ </div><div class="para">
+ <code class="command"><em class="replaceable"><code>Mono-spaced Bold Italic</code></em></code> or <span class="application"><strong><em class="replaceable"><code>Proportional Bold Italic</code></em></strong></span>
+ </div><div class="para">
+ Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ To connect to a remote machine using ssh, type <code class="command">ssh <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>domain.name</code></em></code> at a shell prompt. If the remote machine is <code class="filename">example.com</code> and your username on that machine is john, type <code class="command">ssh john at example.com</code>.
+ </div><div class="para">
+ The <code class="command">mount -o remount <em class="replaceable"><code>file-system</code></em></code> command remounts the named file system. For example, to remount the <code class="filename">/home</code> file system, the command is <code class="command">mount -o remount /home</code>.
+ </div><div class="para">
+ To see the version of a currently installed package, use the <code class="command">rpm -q <em class="replaceable"><code>package</code></em></code> command. It will return a result as follows: <code class="command"><em class="replaceable"><code>package-version-release</code></em></code>.
+ </div></blockquote></div><div class="para">
+ Note the words in bold italics above — username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
+ </div><div class="para">
+ Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ Publican is a <em class="firstterm">DocBook</em> publishing system.
+ </div></blockquote></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Preface-Book_Organization.html"><strong>Prev</strong>4. How to Read this Book</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pr01s05s02.html"><strong>Next</strong>5.2. Pull-quote Conventions</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/pr01s05s02.html b/public_html/en-US/Fedora/21/html/Networking_Guide/pr01s05s02.html
new file mode 100644
index 0000000..c3b998f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/pr01s05s02.html
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2. Pull-quote Conventions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="pr01s05.html" title="5. Document Conventions" /><link rel="prev" href="pr01s05.html" title="5. Document Conventions" /><link rel="next" href="pr01s05s03.html" title="5.3. Notes and Warnings" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s05.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pr01s05s03.html"><strong>Next</strong></a>
</li></ul><div class="section" id="idm225465470032"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225465470032">5.2. Pull-quote Conventions</h3></div></div></div><div class="para">
+ Terminal output and source code listings are set off visually from the surrounding text.
+ </div><div class="para">
+ Output sent to a terminal is set in <code class="computeroutput">mono-spaced roman</code> and presented thus:
+ </div><pre class="screen">books Desktop documentation drafts mss photos stuff svn
+books_tests Desktop1 downloads images notes scripts svgs</pre><div class="para">
+ Source-code listings are also set in <code class="computeroutput">mono-spaced roman</code> but add syntax highlighting as follows:
+ </div><pre class="programlisting">package org.<span class="perl_Function">jboss</span>.<span class="perl_Function">book</span>.<span class="perl_Function">jca</span>.<span class="perl_Function">ex1</span>;
+
+<span class="perl_Keyword">import</span> javax.naming.InitialContext;
+
+<span class="perl_Keyword">public</span> <span class="perl_Keyword">class</span> ExClient
+{
+ <span class="perl_Keyword">public</span> <span class="perl_DataType">static</span> <span class="perl_DataType">void</span> <span class="perl_Function">main</span>(String args[])
+ <span class="perl_Keyword">throws</span> Exception
+ {
+ InitialContext iniCtx = <span class="perl_Keyword">new</span> InitialContext();
+ Object ref = iniCtx.<span class="perl_Function">lookup</span>(<span class="perl_String">"EchoBean"</span>);
+ EchoHome home = (EchoHome) ref;
+ Echo echo = home.<span class="perl_Function">create</span>();
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Created Echo"</span>);
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Echo.echo('Hello') = "</span> + echo.<span class="perl_Function">echo</span>(<span class="perl_String">"Hello"</span>));
+ }
+}</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s05.html"><strong>Prev</strong>5. Document Conventions</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pr01s05s03.html"><strong>Next</strong>5.3. Notes and Warnings</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/pr01s05s03.html b/public_html/en-US/Fedora/21/html/Networking_Guide/pr01s05s03.html
new file mode 100644
index 0000000..db5a328
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/pr01s05s03.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.3. Notes and Warnings</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="pr01s05.html" title="5. Document Conventions" /><link rel="prev" href="pr01s05s02.html" title="5.2. Pull-quote Conventions" /><link rel="next" href="sec-Preface-Feedback.html" title="6. Feedback" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s05s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Preface-Feedback.html"><strong
>Next</strong></a></li></ul><div class="section" id="idm225439621888"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225439621888">5.3. Notes and Warnings</h3></div></div></div><div class="para">
+ Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' will not cause data loss but may cause irritation and frustration.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s05s02.html"><strong>Prev</strong>5.2. Pull-quote Conventions</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Preface-Feedback.html"><strong>Next</strong>6. Feedback</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/pref-Acknowledgments.html b/public_html/en-US/Fedora/21/html/Networking_Guide/pref-Acknowledgments.html
new file mode 100644
index 0000000..b7518ae
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/pref-Acknowledgments.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7. Acknowledgments</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="pr01.html" title="Preface" /><link rel="prev" href="sec-Preface-Feedback.html" title="6. Feedback" /><link rel="next" href="part-Networking.html" title="Part I. Networking" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Preface-Feedback.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="part-Networking.html"><strong>Next</strong></a>
</li></ul><div class="section" id="pref-Acknowledgments"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7. Acknowledgments</h2></div></div></div><div class="para">
+ Certain portions of this text first appeared in the <em class="citetitle">Red Hat Enterprise Linux 6 Deployment Guide</em>, copyright © 2014 Red Hat, Inc., available at <a href="https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/index.html">https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/index.html</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Preface-Feedback.html"><strong>Prev</strong>6. Feedback</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="part-Networking.html"><strong>Next</strong>Part I. Networking</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Activating_a_Channel_Bond.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Activating_a_Channel_Bond.html
new file mode 100644
index 0000000..999cf8b
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Activating_a_Channel_Bond.html
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.3.4. Activating a Channel Bond</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Network_Bonding_Using_the_Command_Line_Interface.html" title="4.3. Using the Command Line Interface (CLI)" /><link rel="prev" href="sec-Creating_SLAVE_Interfaces.html" title="4.3.3. Creating SLAVE Interfaces" /><link rel="next" href="sec-Creating_Multiple_Bonds.html" title="4.3.5. Creating Multiple Bonds" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Cr
eating_SLAVE_Interfaces.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Creating_Multiple_Bonds.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Activating_a_Channel_Bond"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.4. Activating a Channel Bond</h3></div></div></div><div class="para">
+ To activate a bond, bring up all the slaves. As <code class="systemitem">root</code>, issue the following commands:
+<pre class="screen">~]# <code class="command">ifup ifcfg-eth0</code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/7)</pre>
+
+<pre class="screen">~]# <code class="command">ifup ifcfg-eth1</code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/8)</pre>
+ </div><div class="para">
+ Note that if editing interface files for interfaces which are currently <span class="quote">“<span class="quote">up</span>”</span>, set them down first as follows: <pre class="synopsis">ifdown eth<em class="replaceable"><code>N</code></em></pre> Then when complete, bring up all the slaves, which will bring up the bond (provided it was not set <span class="quote">“<span class="quote">down</span>”</span>).
+ </div><div class="para">
+ To make <span class="application"><strong>NetworkManager</strong></span> aware of the changes, issue a command for every changed interface as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">nmcli con load /etc/sysconfig/network-scripts/ifcfg-<em class="replaceable"><code>device</code></em></code></pre>
+ Alternatively, to reload all interfaces:
+<pre class="screen">~]# <code class="command">nmcli con reload</code></pre>
+ The default behavior is for <span class="application"><strong>NetworkManager</strong></span> not to be aware of the changes and to continue using the old configuration data. The is set by the <code class="option">monitor-connection-files</code> option in the <code class="filename">NetworkManager.conf</code> file. See the <code class="filename">NetworkManager.conf(5)</code> manual page for more information.
+ </div><div class="para">
+ To view the status of the bond interface, issue the following command:
+<pre class="screen">~]# <code class="command">ip link show</code>
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 1000
+ link/ether 52:54:00:e9:ce:d2 brd ff:ff:ff:ff:ff:ff
+3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 1000
+ link/ether 52:54:00:38:a6:4c brd ff:ff:ff:ff:ff:ff
+4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT
+ link/ether 52:54:00:38:a6:4c brd ff:ff:ff:ff:ff:ff</pre>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Creating_SLAVE_Interfaces.html"><strong>Prev</strong>4.3.3. Creating SLAVE Interfaces</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Creating_Multiple_Bonds.html"><strong>Next</strong>4.3.5. Creating Multiple Bonds</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Add_a_port_to_a_Network_Team_Using_iputils.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Add_a_port_to_a_Network_Team_Using_iputils.html
new file mode 100644
index 0000000..424b334
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Add_a_port_to_a_Network_Team_Using_iputils.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.3. Add a Port to a Network Team Using iputils</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_a_Network_Team_Using-the_Command_Line.html" title="5.10. Configure a Network Team Using the Command Line" /><link rel="prev" href="sec-Creating_a_Network_Team_Using_ifcfg_Files.html" title="5.10.2. Creating a Network Team Using ifcfg Files" /><link rel="next" href="sec-Listing_the_ports_of_a_Team_Using_teamnl.html" title="5.10.4. Listing the ports of a Team Using teamnl" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" />
</a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Creating_a_Network_Team_Using_ifcfg_Files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Listing_the_ports_of_a_Team_Using_teamnl.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Add_a_port_to_a_Network_Team_Using_iputils"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.3. Add a Port to a Network Team Using iputils</h3></div></div></div><div class="para">
+ To add a port <span class="interface">em1</span> to a network team <span class="interface">team0</span>, using the <span class="application"><strong>ip</strong></span> utility, issue the following commands as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ip link set dev em1 down</code>
+~]# <code class="command">ip link set dev em1 master team0</code></pre>
+ Add additional ports as required. Team driver will bring ports up automatically.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Creating_a_Network_Team_Using_ifcfg_Files.html"><strong>Prev</strong>5.10.2. Creating a Network Team Using ifcfg Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Listing_the_ports_of_a_Team_Using_teamnl.html"><strong>Next</strong>5.10.4. Listing the ports of a Team Using teamnl</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Add_an_address_to_a_Network_Team_Using_iputils.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Add_an_address_to_a_Network_Team_Using_iputils.html
new file mode 100644
index 0000000..c87b918
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Add_an_address_to_a_Network_Team_Using_iputils.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.6. Add an Address to a Network Team Using iputils</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_a_Network_Team_Using-the_Command_Line.html" title="5.10. Configure a Network Team Using the Command Line" /><link rel="prev" href="sec-Configuring_Options_of_a_Team_Using_teamnl.html" title="5.10.5. Configuring Options of a Team Using teamnl" /><link rel="next" href="sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils.html" title="5.10.7. Bring up an Interface to a Network Team Using iputils" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png"
alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Options_of_a_Team_Using_teamnl.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Add_an_address_to_a_Network_Team_Using_iputils"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.6. Add an Address to a Network Team Using iputils</h3></div></div></div><div class="para">
+ To add an address to a team <span class="interface">team0</span>, using the <span class="application"><strong>ip</strong></span> utility, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ip addr add 192.168.252.2/24 dev team0</code></pre>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Options_of_a_Team_Using_teamnl.html"><strong>Prev</strong>5.10.5. Configuring Options of a Team Using teamnl</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils.html"><strong>Next</strong>5.10.7. Bring up an Interface to a Network Team U...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team.html
new file mode 100644
index 0000000..536ea92
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.11.3. Apply a Configuration to a Port in a Network Team</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Controlling_teamd_with_teamdctl.html" title="5.11. Controlling teamd with teamdctl" /><link rel="prev" href="sec-Remove_a_Port_From_a_Network_Team.html" title="5.11.2. Remove a Port From a Network Team" /><link rel="next" href="sec-View_the_Configuration_of_a_Port_in_a_Network_Team.html" title="5.11.4. View the Configuration of a Port in a Network Team" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><
li class="previous"><a accesskey="p" href="sec-Remove_a_Port_From_a_Network_Team.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-View_the_Configuration_of_a_Port_in_a_Network_Team.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.11.3. Apply a Configuration to a Port in a Network Team</h3></div></div></div><div class="para">
+ To apply a JSON format configuration to a port <span class="interface">em1</span> in a network team <span class="interface">team0</span>, issue a command as <code class="systemitem">root</code> in the following format:
+<pre class="screen">~]# <code class="command">teamdctl team0 port config update em1 <em class="replaceable"><code>JSON-config-string</code></em></code></pre>
+ Where <em class="replaceable"><code>JSON-config-string</code></em> is the configuration as a string of text in JSON format. This will update the configuration of the port using the JSON format string supplied. An example of a valid JSON string for configuring a port would be the following:
+<pre class="screen">
+{
+ "prio": -10,
+ "sticky": true
+}</pre>
+ Use single quotes around the JSON configuration string and omit the line breaks.
+ </div><div class="para">
+ Note that the old configuration will be overwritten and that any options omitted will be reset to the default values. See the <code class="filename">teamdctl(8)</code> man page for more team daemon control tool command examples.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Remove_a_Port_From_a_Network_Team.html"><strong>Prev</strong>5.11.2. Remove a Port From a Network Team</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-View_the_Configuration_of_a_Port_in_a_Network_Team.html"><strong>Next</strong>5.11.4. View the Configuration of a Port in a Net...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-BIND.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-BIND.html
new file mode 100644
index 0000000..af69b34
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-BIND.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.2. BIND</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-DNS_Servers.html" title="Chapter 10. DNS Servers" /><link rel="prev" href="ch-DNS_Servers.html" title="Chapter 10. DNS Servers" /><link rel="next" href="sec-bind-namedconf.html" title="10.2.2. Configuring the named Service" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-DNS_Servers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" hre
f="sec-bind-namedconf.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="sec-BIND" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.2. BIND</h2></div></div></div><a id="idm225485884304" class="indexterm"></a><div class="para">
+ This section covers <code class="systemitem">BIND</code> (Berkeley Internet Name Domain), the <code class="systemitem">DNS</code> server included in Fedora. It focuses on the structure of its configuration files, and describes how to administer it both locally and remotely.
+ </div><div class="section" id="sec-bind-empty-zones"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.1. Empty Zones</h3></div></div></div><div class="para">
+ <code class="systemitem">BIND</code> configures a number of <span class="quote">“<span class="quote">empty zones</span>”</span> to prevent recursive servers from sending unnecessary queries to Internet servers that cannot handle them (thus creating delays and SERVFAIL responses to clients who query for them). These empty zones ensure that immediate and authoritative NXDOMAIN responses are returned instead. The configuration option <code class="command">empty-zones-enable</code> controls whether or not empty zones are created, whilst the option <code class="command">disable-empty-zone</code> can be used in addition to disable one or more empty zones from the list of default prefixes that would be used.
+ </div><div class="para">
+ The number of empty zones created for <a href="http://www.rfc-editor.org/info/rfc1918"><em class="citetitle">RFC 1918</em></a> prefixes has been increased, and users of <code class="systemitem">BIND 9.9</code> and above will see the <a href="http://www.rfc-editor.org/info/rfc1918"><em class="citetitle">RFC 1918</em></a> empty zones both when <code class="command">empty-zones-enable</code> is unspecified (defaults to <code class="literal">yes</code>), and when it is explicitly set to <code class="literal">yes</code>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-DNS_Servers.html"><strong>Prev</strong>Chapter 10. DNS Servers</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-bind-namedconf.html"><strong>Next</strong>10.2.2. Configuring the named Service</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils.html
new file mode 100644
index 0000000..212684c
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.7. Bring up an Interface to a Network Team Using iputils</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_a_Network_Team_Using-the_Command_Line.html" title="5.10. Configure a Network Team Using the Command Line" /><link rel="prev" href="sec-Add_an_address_to_a_Network_Team_Using_iputils.html" title="5.10.6. Add an Address to a Network Team Using iputils" /><link rel="next" href="sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl.html" title="5.10.8. Viewing the Active Port Options of a Team Using teamnl" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.p
ng" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Add_an_address_to_a_Network_Team_Using_iputils.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.7. Bring up an Interface to a Network Team Using iputils</h3></div></div></div><div class="para">
+ To activate or <span class="quote">“<span class="quote">bring up</span>”</span> an interface to a network team, <span class="interface">team0</span>, using the <span class="application"><strong>ip</strong></span> utility, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ip link set team0 up</code></pre>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Add_an_address_to_a_Network_Team_Using_iputils.html"><strong>Prev</strong>5.10.6. Add an Address to a Network Team Using ip...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl.html"><strong>Next</strong>5.10.8. Viewing the Active Port Options of a Team...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Comparison_of_Network_Teaming_to_Bonding.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Comparison_of_Network_Teaming_to_Bonding.html
new file mode 100644
index 0000000..03a39aa
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Comparison_of_Network_Teaming_to_Bonding.html
@@ -0,0 +1,177 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2. Comparison of Network Teaming to Bonding</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Teaming.html" title="Chapter 5. Configure Network Teaming" /><link rel="prev" href="ch-Configure_Network_Teaming.html" title="Chapter 5. Configure Network Teaming" /><link rel="next" href="sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces.html" title="5.3. Understanding the Default Behavior of Master and Slave Interfaces" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul clas
s="docnav"><li class="previous"><a accesskey="p" href="ch-Configure_Network_Teaming.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Comparison_of_Network_Teaming_to_Bonding"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. Comparison of Network Teaming to Bonding</h2></div></div></div><div class="table" id="Bonding_Teaming_Comparison"><h6>Table 5.1. A Comparison of Features in Bonding and Team</h6><div class="table-contents"><table summary="A Comparison of Features in Bonding and Team" border="1"><colgroup><col align="left" class="c1" width="33%" /><col align="left" class="c2" width="33%" /><col align="left" class="c3" width="33%" /></colgroup><thead><tr><th class="" align="left">
+ Feature
+ </th><th class="" align="left">
+ Bonding
+ </th><th class="" align="left">
+ Team
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ broadcast Tx policy
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ round-robin Tx policy
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ active-backup Tx policy
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ LACP (802.3ad) support
+ </td><td class="" align="left">
+ Yes (passive only)
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ Hash-based Tx policy
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ User can set hash function
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ Tx load-balancing support (TLB)
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ LACP hash port select
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ load-balancing for LACP support
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ Ethtool link monitoring
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ ARP link monitoring
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ NS/NA (IPv6) link monitoring
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ ports up/down delays
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ port priorities and stickiness (<span class="quote">“<span class="quote">primary</span>”</span> option enhancement)
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ separate per-port link monitoring setup
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ multiple link monitoring setup
+ </td><td class="" align="left">
+ Limited
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ lockless Tx/Rx path
+ </td><td class="" align="left">
+ No (rwlock)
+ </td><td class="" align="left">
+ Yes (RCU)
+ </td></tr><tr><td class="" align="left">
+ VLAN support
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ user-space runtime control
+ </td><td class="" align="left">
+ Limited
+ </td><td class="" align="left">
+ Full
+ </td></tr><tr><td class="" align="left">
+ Logic in user-space
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ Extensibility
+ </td><td class="" align="left">
+ Hard
+ </td><td class="" align="left">
+ Easy
+ </td></tr><tr><td class="" align="left">
+ Modular design
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ Performance overhead
+ </td><td class="" align="left">
+ Low
+ </td><td class="" align="left">
+ Very Low
+ </td></tr><tr><td class="" align="left">
+ D-Bus interface
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ multiple device stacking
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ zero config using LLDP
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ (in planning)
+ </td></tr><tr><td class="" align="left">
+ NetworkManager support
+ </td><td class="" align="left">
+ Yes
+ </td><td class="" align="left">
+ Yes
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Configure_Network_Teaming.html"><strong>Prev</strong>Chapter 5. Configure Network Teaming</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces.html"><strong>Next</strong>5.3. Understanding the Default Behavior of Master...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging-additional_resources.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging-additional_resources.html
new file mode 100644
index 0000000..555855c
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging-additional_resources.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.5. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_802_1Q_VLAN_Tagging.html" title="Chapter 7. Configure 802.1Q VLAN tagging" /><link rel="prev" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli.html" title="7.4. Configure 802.1Q VLAN Tagging Using the Command Line Tool, nmcli" /><link rel="next" href="ch-Consistent_Network_Device_Naming.html" title="Chapter 8. Consistent Network Device Naming" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></
a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Consistent_Network_Device_Naming.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_802_1Q_VLAN_Tagging-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.5. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding Network Teaming.
+ </div><div class="section" id="sec-Configure_802_1Q_VLAN_Tagging-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.5.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">ip-link(8)</code> man page — Describes the <span class="application"><strong>ip</strong></span> utility's network device configuration commands.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nmcli(1)</code> man page — Describes <span class="application"><strong>NetworkManager</strong></span>'s command‐line tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nmcli-examples(5)</code> man page — Gives examples of <span class="application"><strong>nmcli</strong></span> commands.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nm-settings(5)</code> man page — Description of settings and parameters of <span class="application"><strong>NetworkManager</strong></span> connections.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli.html"><strong>Prev</strong>7.4. Configure 802.1Q VLAN Tagging Using the Comm...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Consistent_Network_Device_Naming.html"><strong>Next</strong>Chapter 8. Consistent Network Device Naming</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html
new file mode 100644
index 0000000..a0acc0e
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2. Configure 802.1Q VLAN Tagging Using a GUI</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_802_1Q_VLAN_Tagging.html" title="Chapter 7. Configure 802.1Q VLAN tagging" /><link rel="prev" href="ch-Configure_802_1Q_VLAN_Tagging.html" title="Chapter 7. Configure 802.1Q VLAN tagging" /><link rel="next" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html" title="7.3. Configure 802.1Q VLAN Tagging Using the Command Line" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="ch-Configure_802_1Q_VLAN_Tagging.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.2. Configure 802.1Q VLAN Tagging Using a GUI</h2></div></div></div><div class="section" id="sec-Establishing_a_VLAN_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.1. Establishing a VLAN Connection</h3></div></div></div><div class="para">
+ You can use the GNOME <span class="application"><strong>control-center</strong></span> utility to direct <span class="application"><strong>NetworkManager</strong></span> to create a VLAN using an existing interface as the parent interface. At time of writing, you can only make VLANs on Ethernet devices. Note that VLAN devices are only created automatically if the parent interface is set to connect automatically.
+ </div><div class="procedure" id="procedure-Adding_a_New_VLAN_Connection"><h6>Procedure 7.1. Adding a New VLAN Connection</h6><div class="para">
+ You can configure a VLAN connection by opening the <span class="guilabel"><strong>Network</strong></span> window, clicking the plus symbol, and selecting <span class="guilabel"><strong>VLAN</strong></span> from the list.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Click the plus symbol to open the selection list. Select <span class="guilabel"><strong>VLAN</strong></span>. The <span class="guilabel"><strong>Editing VLAN Connection <em class="replaceable"><code>1</code></em></strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ On the <span class="guilabel"><strong>VLAN</strong></span> tab, select the parent interface from the drop-down list you want to use for the VLAN connection.
+ </div></li><li class="step"><div class="para">
+ Enter the VLAN ID
+ </div></li><li class="step"><div class="para">
+ Enter a VLAN interface name. This is the name of the VLAN interface that will be created. For example, <code class="literal">eth0.1</code> or <code class="literal">vlan2</code>. (Normally this is either the parent interface name plus <span class="quote">“<span class="quote"><code class="literal">.</code></span>”</span> and the VLAN ID, or <span class="quote">“<span class="quote"><code class="literal">vlan</code></span>”</span> plus the VLAN ID.)
+ </div></li><li class="step"><div class="para">
+ Review and confirm the settings and then click the <span class="guilabel"><strong>Save</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ To edit the VLAN-specific settings see <a class="xref" href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html#sec-Configuring_the_VLAN_Tab">Section 7.2.1.1, “Configuring the VLAN Tab”</a>.
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_VLAN_Connection"><h6>Procedure 7.2. Editing an Existing VLAN Connection</h6><div class="para">
+ Follow these steps to edit an existing VLAN connection.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the connection you want to edit and click the <span class="guilabel"><strong>Options</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>General</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Configure the connection name, auto-connect behavior, and availability settings.
+ </div><div class="para">
+ These settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the <span class="guilabel"><strong>VLAN</strong></span> section of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to this network when it is available</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. Refer to <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="sec-System-wide_and_Private_Connection_Profiles.html">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li></ul></div></li><li class="step"><div class="para">
+ To edit the VLAN-specific settings see <a class="xref" href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html#sec-Configuring_the_VLAN_Tab">Section 7.2.1.1, “Configuring the VLAN Tab”</a>.
+ </div></li></ol></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-VLAN">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your VLAN connection, click the <span class="guibutton"><strong>Save</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network</strong></span> window and clicking <span class="guilabel"><strong>Options</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>.
+ </div></li></ul></div><div class="section" id="sec-Configuring_the_VLAN_Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.2.1.1. Configuring the VLAN Tab</h4></div></div></div><div class="para">
+ If you have already added a new VLAN connection (refer to <a class="xref" href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html#procedure-Adding_a_New_VLAN_Connection">Procedure 7.1, “Adding a New VLAN Connection”</a> for instructions), you can edit the <span class="guilabel"><strong>VLAN</strong></span> tab to set the parent interface and the VLAN ID.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Parent Interface</strong></span> </span></dt><dd><div class="para">
+ A previously configured interface can be selected in the drop-down list.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>VLAN ID</strong></span> </span></dt><dd><div class="para">
+ The identification number to be used to tag the VLAN network traffic.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>VLAN interface name</strong></span> </span></dt><dd><div class="para">
+ The name of the VLAN interface that will be created. For example, <code class="literal">eth0.1</code> or <code class="literal">vlan2</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Cloned MAC address</strong></span> </span></dt><dd><div class="para">
+ Optionally sets an alternate MAC address to use for identifying the VLAN interface. This can be used to change the source MAC address for packets sent on this VLAN.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>MTU</strong></span> </span></dt><dd><div class="para">
+ Optionally sets a Maximum Transmission Unit (MTU) size to be used for packets to be sent over the VLAN connection.
+ </div></dd></dl></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Configure_802_1Q_VLAN_Tagging.html"><strong>Prev</strong>Chapter 7. Configure 802.1Q VLAN tagging</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html"><strong>Next</strong>7.3. Configure 802.1Q VLAN Tagging Using the Comm...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html
new file mode 100644
index 0000000..3023131
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3. Configure 802.1Q VLAN Tagging Using the Command Line</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_802_1Q_VLAN_Tagging.html" title="Chapter 7. Configure 802.1Q VLAN tagging" /><link rel="prev" href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html" title="7.2. Configure 802.1Q VLAN Tagging Using a GUI" /><link rel="next" href="sec-Configure_802_1Q_VLAN_Tagging_ip_Commands.html" title="7.3.2. Configure 802.1Q VLAN Tagging Using ip Commands" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav">
<li class="previous"><a accesskey="p" href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_802_1Q_VLAN_Tagging_ip_Commands.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.3. Configure 802.1Q VLAN Tagging Using the Command Line</h2></div></div></div><div class="para">
+ In Fedora, the <code class="systemitem">8021q</code> module is loaded by default. If necessary, you can make sure that the module is loaded by issuing the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">modprobe --first-time 8021q</code>
+modprobe: ERROR: could not insert '8021q': Module already in kernel</pre>
+ To display information about the module, issue the following command:
+<pre class="screen">~]$ <code class="command">modinfo 8021q</code></pre>
+ See the <code class="filename">modprobe(8)</code> man page for more command options.
+ </div><div class="section" id="sec-Setting_Up_802.1Q_VLAN_Tagging_Using_ifcfg_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.1. Setting Up 802.1Q VLAN Tagging Using ifcfg Files</h3></div></div></div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Configure the parent interface in <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth<em class="replaceable"><code>X</code></em></code>, where <em class="replaceable"><code>X</code></em> is a unique number corresponding to a specific interface, as follows:
+ </div><pre class="screen">DEVICE=ethX
+TYPE=Ethernet
+BOOTPROTO=none
+ONBOOT=yes</pre></li><li class="step"><div class="para">
+ Configure the VLAN interface configuration in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory. The configuration file name should be the parent interface plus a <code class="literal">.</code> character plus the VLAN ID number. For example, if the VLAN ID is 192, and the parent interface is <em class="replaceable"><code>eth0</code></em>, then the configuration file name should be <code class="filename">ifcfg-eth0.192</code>:
+ </div><pre class="screen">DEVICE=ethX.192
+BOOTPROTO=none
+ONBOOT=yes
+IPADDR=192.168.1.1
+PREFIX=24
+NETWORK=192.168.1.0
+VLAN=yes</pre><div class="para">
+ If there is a need to configure a second VLAN, with for example, VLAN ID 193, on the same interface, <em class="replaceable"><code>eth0</code></em>, add a new file with the name <code class="filename">eth0.193</code> with the VLAN configuration details.
+ </div></li><li class="step"><div class="para">
+ Restart the networking service in order for the changes to take effect. As <code class="systemitem">root</code> issue the following command:
+ </div><pre class="screen">~]# <code class="command">systemctl restart network</code></pre></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html"><strong>Prev</strong>7.2. Configure 802.1Q VLAN Tagging Using a GUI</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_802_1Q_VLAN_Tagging_ip_Commands.html"><strong>Next</strong>7.3.2. Configure 802.1Q VLAN Tagging Using ip Com...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli.html
new file mode 100644
index 0000000..dbecbd6
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli.html
@@ -0,0 +1,119 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.4. Configure 802.1Q VLAN Tagging Using the Command Line Tool, nmcli</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_802_1Q_VLAN_Tagging.html" title="Chapter 7. Configure 802.1Q VLAN tagging" /><link rel="prev" href="sec-Configure_802_1Q_VLAN_Tagging_ip_Commands.html" title="7.3.2. Configure 802.1Q VLAN Tagging Using ip Commands" /><link rel="next" href="sec-Configure_802_1Q_VLAN_Tagging-additional_resources.html" title="7.5. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="p
revious"><a accesskey="p" href="sec-Configure_802_1Q_VLAN_Tagging_ip_Commands.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_802_1Q_VLAN_Tagging-additional_resources.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.4. Configure 802.1Q VLAN Tagging Using the Command Line Tool, nmcli</h2></div></div></div><div class="para">
+ To view the available interfaces on the system, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con show</code>
+NAME UUID TYPE DEVICE
+System eth1 9c92fad9-6ecb-3e6c-eb4d-8a47c6f50c04 802-3-ethernet eth1
+System eth0 5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 802-3-ethernet eth0</pre>
+ Note that the NAME field in the output always denotes the connection ID. It is not the interface name even though it might look the same. The ID can be used in <code class="command">nmcli connection</code> commands to identify a connection. Use the DEVICE name with other applications such as <code class="systemitem">firewalld</code>.
+ </div><div class="para">
+ To create an 802.1Q VLAN interface on Ethernet interface <em class="replaceable"><code>eth0</code></em>, with VLAN interface <em class="replaceable"><code>VLAN10</code></em> and ID <code class="literal">10</code>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type vlan ifname <em class="replaceable"><code>VLAN10</code></em> dev <em class="replaceable"><code>eth0</code></em> id 10</code>
+Connection 'vlan-VLAN10' (37750b4a-8ef5-40e6-be9b-4fb21a4b6d17) successfully added.</pre>
+ Note that as no <code class="option">con-name</code> was given for the VLAN interface, the name was derived from the interface name by prepending the type. Alternatively, specify a name with the <code class="option">con-name</code> option as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type vlan con-name <em class="replaceable"><code>VLAN12</code></em> dev <em class="replaceable"><code>eth0</code></em> id 12</code>
+Connection 'VLAN12' (b796c16a-9f5f-441c-835c-f594d40e6533) successfully added.</pre>
+ </div><h3 id="bh-Assigning_Addresses_to_VLAN_Interfaces">Assigning Addresses to VLAN Interfaces</h3><div class="para">
+ You can use the same <span class="application"><strong>nmcli</strong></span> commands to assign static and dynamic interface addresses as with any other interface.
+ </div><div class="para">
+ For example, a command to create a VLAN interface with a static <code class="systemitem">IPv4</code> address and gateway is as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type vlan con-name <em class="replaceable"><code>VLAN20</code></em> ifname <em class="replaceable"><code>eth0</code></em> ip4 10.10.10.10/24 \</code>
+<code class="command">gw4 10.10.10.254</code></pre>
+ </div><div class="para">
+ To create a VLAN interface with dynamically assigned addressing, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type vlan con-name <em class="replaceable"><code>VLAN30</code></em> ifname <em class="replaceable"><code>eth0</code></em></code></pre>
+
+ </div><div class="para">
+ See <a class="xref" href="sec-Connecting_to_a_Network_Using_nmcli.html">Section 2.4.2, “Connecting to a Network Using nmcli”</a> for examples of using <span class="application"><strong>nmcli</strong></span> commands to configure interfaces.
+ </div><div class="para">
+ To review the VLAN interfaces created, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con show</code>
+NAME UUID TYPE DEVICE
+VLAN12 4129a37d-4feb-4be5-ac17-14a193821755 vlan eth0.12
+System eth1 9c92fad9-6ecb-3e6c-eb4d-8a47c6f50c04 802-3-ethernet eth1
+System eth0 5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 802-3-ethernet eth0
+vlan-VLAN10 1be91581-11c2-461a-b40d-893d42fed4f4 vlan VLAN10</pre>
+
+ </div><div class="para">
+ To view detailed information about the newly configured connection, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli -p con show <em class="replaceable"><code>VLAN12</code></em></code>
+===============================================================================
+ Connection profile details (VLAN12)
+===============================================================================
+connection.id: VLAN12
+connection.uuid: 4129a37d-4feb-4be5-ac17-14a193821755
+connection.interface-name: --
+connection.type: vlan
+connection.autoconnect: yes
+<em class="lineannotation"><span class="lineannotation">…</span></em>
+-------------------------------------------------------------------------------
+802-3-ethernet.port: --
+802-3-ethernet.speed: 0
+802-3-ethernet.duplex: --
+802-3-ethernet.auto-negotiate: yes
+802-3-ethernet.mac-address: --
+802-3-ethernet.cloned-mac-address: --
+802-3-ethernet.mac-address-blacklist:
+802-3-ethernet.mtu: auto
+<em class="lineannotation"><span class="lineannotation">…</span></em>
+vlan.interface-name: --
+vlan.parent: eth0
+vlan.id: 12
+vlan.flags: 0 (NONE)
+vlan.ingress-priority-map:
+vlan.egress-priority-map:
+-------------------------------------------------------------------------------
+===============================================================================
+ Activate connection details (4129a37d-4feb-4be5-ac17-14a193821755)
+===============================================================================
+GENERAL.NAME: VLAN12
+GENERAL.UUID: 4129a37d-4feb-4be5-ac17-14a193821755
+GENERAL.DEVICES: eth0.12
+GENERAL.STATE: activating
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em></pre>
+ </div><div class="para">
+ Further options for the VLAN command are listed in the VLAN section of the <code class="filename">nmcli(1)</code> man page. In the man pages the device on which the VLAN is created is referred to as the parent device. In the example above the device was specified by its interface name, <code class="literal">eth0</code>, it can also be specified by the connection UUID or MAC address.
+ </div><div class="para">
+ To create an 802.1Q VLAN connection profile with ingress priority mapping on Ethernet interface <em class="replaceable"><code>eth1</code></em>, with name <span class="interface">VLAN1</span> and ID <code class="literal">13</code>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type vlan con-name <em class="replaceable"><code>VLAN1</code></em> dev <em class="replaceable"><code>eth2</code></em> id 13 ingress "2:3,3:5"</code></pre>
+
+ </div><div class="para">
+ To view all the parameters associated with the VLAN created above, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection show <em class="replaceable"><code>vlan-VLAN10</code></em></code></pre>
+
+ </div><div class="para">
+ To change the MTU, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection modify <em class="replaceable"><code>vlan-VLAN10</code></em> 802.mtu 1496</code></pre>
+ The MTU setting determines the maximum size of the network layer packet. The maximum size of the payload the link-layer frame can carry in turn limits the network layer MTU. For standard Ethernet frames this means an MTU of 1500 bytes. It should not be necessary to change the MTU when setting up a VLAN as the link-layer header is increased in size by 4 bytes to accommodate the 802.1Q tag.
+ </div><div class="para">
+ At time of writing, <code class="literal">connection.interface-name</code> and <code class="literal">vlan.interface-name</code> have to be the same (if they are set). They must therefore be changed simultaneously using <span class="application"><strong>nmcli</strong></span>'s interactive mode. To change a VLAN connections name, issue commands as follows:
+<pre class="screen">~]$ <code class="command">nmcli con edit <em class="replaceable"><code>vlan-VLAN10</code></em></code>
+nmcli> <code class="command">set vlan.interface-name <em class="replaceable"><code>superVLAN</code></em></code>
+nmcli> <code class="command">set connection.interface-name <em class="replaceable"><code>superVLAN</code></em></code>
+nmcli> <code class="command">save</code>
+nmcli> <code class="command">quit</code></pre>
+
+ </div><div class="para">
+ The <span class="application"><strong>nmcli</strong></span> utility can be used to set and clear <code class="literal">ioctl</code> flags which change the way the 802.1Q code functions. The following VLAN flags are supported by <span class="application"><strong>NetworkManager</strong></span>:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 0x01 - reordering of output packet headers
+ </div></li><li class="listitem"><div class="para">
+ 0x02 - use GVRP protocol
+ </div></li><li class="listitem"><div class="para">
+ 0x04 - loose binding of the interface and its master
+ </div></li></ul></div>
+ The state of the VLAN is synchronized to the state of the parent or master interface (the interface or device on which the VLAN is created). If the parent interface is set to the <span class="quote">“<span class="quote">down</span>”</span> administrative state then all associated VLANs are set down and all routes are flushed from the routing table. Flag <code class="literal">0x04</code> enables a <em class="firstterm">loose binding</em> mode, in which only the operational state is passed from the parent to the associated VLANs, but the VLAN device state is not changed.
+ </div><div class="para">
+ To set a VLAN flag, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection modify vlan-VLAN10 vlan.flags 1</code></pre>
+
+ </div><div class="para">
+ See <a class="xref" href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html">Section 2.4, “Using the NetworkManager Command Line Tool, nmcli”</a> for an introduction to <span class="application"><strong>nmcli</strong></span>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_802_1Q_VLAN_Tagging_ip_Commands.html"><strong>Prev</strong>7.3.2. Configure 802.1Q VLAN Tagging Using ip Com...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_802_1Q_VLAN_Tagging-additional_resources.html"><strong>Next</strong>7.5. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_ip_Commands.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_ip_Commands.html
new file mode 100644
index 0000000..794d326
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_802_1Q_VLAN_Tagging_ip_Commands.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.2. Configure 802.1Q VLAN Tagging Using ip Commands</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html" title="7.3. Configure 802.1Q VLAN Tagging Using the Command Line" /><link rel="prev" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html" title="7.3. Configure 802.1Q VLAN Tagging Using the Command Line" /><link rel="next" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli.html" title="7.4. Configure 802.1Q VLAN Tagging Using the Command Line Tool, nmcli" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img
src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_802_1Q_VLAN_Tagging_ip_Commands"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.2. Configure 802.1Q VLAN Tagging Using ip Commands</h3></div></div></div><div class="para">
+ To create an 802.1Q VLAN interface on Ethernet interface <em class="replaceable"><code>eth0</code></em>, with name <em class="replaceable"><code>VLAN8</code></em> and ID <code class="literal">8</code>, issue a command as <code class="systemitem">root</code> as follows:
+<pre class="screen">~]# <code class="command">ip link add link <em class="replaceable"><code>eth0</code></em> name <em class="replaceable"><code>eth0.8</code></em> type vlan id 8</code></pre>
+ To view the VLAN, issue the following command:
+<pre class="screen">~]$ <code class="command">ip -d link show <em class="replaceable"><code>eth0.8</code></em></code>
+4: eth0.8 at eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT
+ link/ether 52:54:00:ce:5f:6c brd ff:ff:ff:ff:ff:ff promiscuity 0
+ vlan protocol 802.1Q id 8 <REORDER_HDR></pre>
+ </div><div class="para">
+ Note that the <span class="application"><strong>ip</strong></span> utility interprets the VLAN ID as a hexadecimal value if it is preceded by <code class="literal">0x</code> and as an octal value if it has a leading <code class="literal">0</code>. This means that in order to assign a VLAN ID with a decimal value of <code class="literal">22</code>, you must not add any leading zeros.
+ </div><div class="para">
+ To remove the VLAN, issue a command as <code class="systemitem">root</code> as follows:
+<pre class="screen">~]# <code class="command">ip link delete <em class="replaceable"><code>eth0.8</code></em></code></pre>
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ VLAN interfaces created using <span class="application"><strong>ip</strong></span> commands at the command prompt will be lost if the system is shutdown or restarted. To configure VLAN interfaces to be persistent after a system restart, use <code class="filename">ifcfg</code> files. See <a class="xref" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html#sec-Setting_Up_802.1Q_VLAN_Tagging_Using_ifcfg_Files">Section 7.3.1, “Setting Up 802.1Q VLAN Tagging Using ifcfg Files”</a>
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line.html"><strong>Prev</strong>7.3. Configure 802.1Q VLAN Tagging Using the Comm...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line_Tool_nmcli.html"><strong>Next</strong>7.4. Configure 802.1Q VLAN Tagging Using the Comm...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm.html
new file mode 100644
index 0000000..ded5e4f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.12.9. Configure BPF-based Tx Port Selectors</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_teamd_Runners.html" title="5.12. Configure teamd Runners" /><link rel="prev" href="sec-Configure_Port_Selection_Override.html" title="5.12.8. Configure Port Selection Override" /><link rel="next" href="sec-Configure_Network_Teaming_Using_nmcli.html" title="5.13. Configure Network Teaming Using nmcli" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s
ec-Configure_Port_Selection_Override.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_Network_Teaming_Using_nmcli.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.9. Configure BPF-based Tx Port Selectors</h3></div></div></div><div class="para">
+ The loadbalance and LACP runners uses hashes of packets to sort network traffic flow. The hash computation mechanism is based on the <em class="firstterm">Berkeley Packet Filter</em> (<acronym class="acronym">BPF</acronym>) code. The BPF code is used to generate a hash rather than make a policy decision for outgoing packets. The hash length is 8 bits giving 256 variants. This means many different <em class="firstterm">socket buffers</em> (<acronym class="acronym">SKB</acronym>) can have the same hash and therefore pass traffic over the same link. The use of a short hash is a quick way to sort traffic into different streams for the purposes of load balancing across multiple links. In static mode, the hash is only used to decide out of which port the traffic should be sent. In active mode, the runner will continually reassign hashes to different ports in an attempt to reach a perfect balance.
+ </div><div class="para">
+ The following fragment types or strings can be used for packet Tx hash computation:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">eth</code> — Uses source and destination MAC addresses.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">vlan</code> — Uses VLAN ID.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">ipv4</code> — Uses source and destination <code class="systemitem">IPv4</code> addresses.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">ipv6</code> — Uses source and destination <code class="systemitem">IPv6</code> addresses.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">ip</code> — Uses source and destination <code class="systemitem">IPv4</code> and <code class="systemitem">IPv6</code> addresses.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">l3</code> — Uses source and destination <code class="systemitem">IPv4</code> and <code class="systemitem">IPv6</code> addresses.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">tcp</code> — Uses source and destination <code class="systemitem">TCP</code> ports.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">udp</code> — Uses source and destination <code class="systemitem">UDP</code> ports.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">sctp</code> — Uses source and destination <code class="systemitem">SCTP</code> ports.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">l4</code> — Uses source and destination <code class="systemitem">TCP</code> and <code class="systemitem">UDP</code> and <code class="systemitem">SCTP</code> ports.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ These strings can be used by adding a line in the following format to the load balance runner: <pre class="synopsis">"tx_hash": ["eth", "ipv4", "ipv6"]</pre> See <a class="xref" href="sec-Configure_the_loadbalance_Runner.html">Section 5.12.5, “Configure the loadbalance Runner”</a> for an example.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_Port_Selection_Override.html"><strong>Prev</strong>5.12.8. Configure Port Selection Override</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_Network_Teaming_Using_nmcli.html"><strong>Next</strong>5.13. Configure Network Teaming Using nmcli</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Monitoring_of_the_Link_State.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Monitoring_of_the_Link_State.html
new file mode 100644
index 0000000..a3c6f78
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Monitoring_of_the_Link_State.html
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.12.7. Configure Monitoring of the Link State</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_teamd_Runners.html" title="5.12. Configure teamd Runners" /><link rel="prev" href="sec-Configure_the_LACP_Runner.html" title="5.12.6. Configure the LACP (802.3ad) Runner" /><link rel="next" href="sec-Configure_Port_Selection_Override.html" title="5.12.8. Configure Port Selection Override" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure
_the_LACP_Runner.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_Port_Selection_Override.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_Monitoring_of_the_Link_State"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.7. Configure Monitoring of the Link State</h3></div></div></div><div class="para">
+ The following methods of link state monitoring are available. To implement one of the methods, add the JSON format string to the team JSON format configuration file using an editor running with <code class="systemitem">root</code> privileges.
+ </div><div class="section" id="sec-Configure_Ethtool_for_Link-state_Monitoring"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">5.12.7.1. Configure Ethtool for link-state Monitoring</h4></div></div></div><div class="para">
+ To add or edit an existing delay, in milliseconds, between the link coming up and the runner being notified about it, add or edit a section as follows:
+<pre class="screen">
+"link_watch": {
+ "name": "ethtool",
+ "delay_up": 2500
+}</pre>
+
+ </div><div class="para">
+ To add or edit an existing delay, in milliseconds, between the link going down and the runner being notified about it, add or edit a section as follows:
+<pre class="screen">
+"link_watch": {
+ "name": "ethtool",
+ "delay_down": 1000
+}</pre>
+
+ </div></div><div class="section" id="sec-Configure_ARP_Ping_for_Link-state_Monitoring"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">5.12.7.2. Configure ARP Ping for Link-state Monitoring</h4></div></div></div><div class="para">
+ The team daemon <code class="systemitem">teamd</code> sends an ARP REQUEST to an address at the remote end of the link in order to determine if the link is up. The method used is the same as the <span class="application"><strong>arping</strong></span> utility but it does not use that utility.
+ </div><div class="para">
+ Prepare a file containing the new configuration in JSON format similar to the following example:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {"name": "activebackup"},
+ "link_watch":{
+ "name": "arp_ping",
+ "interval": 100,
+ "missed_max": 30,
+ "source_host": "192.168.23.2",
+ "target_host": "192.168.23.1"
+ },
+ "ports": {
+ "em1": {
+ "prio": -10,
+ "sticky": true
+ },
+ "em2": {
+ "prio": 100
+ }
+ }
+}</pre>
+ This configuration uses <span class="application"><strong>arp_ping</strong></span> as the link watcher. The <code class="option">missed_max</code> option is a limit value of the maximum allowed number of missed replies (ARP replies for example). It should be chosen in conjunction with the <code class="option">interval</code> option in order to determine the total time before a link is reported as down.
+ </div><div class="para">
+ To load a new configuration for a team port <span class="interface">em2</span>, from a file containing a JSON configuration, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# port config update em2 <em class="replaceable"><code>JSON-config-file</code></em></pre>
+ Note that the old configuration will be overwritten and that any options omitted will be reset to the default values. See the <code class="filename">teamdctl(8)</code> man page for more team daemon control tool command examples.
+ </div></div><div class="section" id="sec-Configure_IPv6_NA_NS_for_Link-state_Monitoring"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">5.12.7.3. Configure IPv6 NA/NS for Link-state Monitoring</h4></div></div></div><div class="para">
+
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {"name": "activebackup"},
+ "link_watch": {
+ "name": "nsna_ping",
+ "interval": 200,
+ "missed_max": 15,
+ "target_host": "fe80::210:18ff:feaa:bbcc"
+ },
+ "ports": {
+ "em1": {
+ "prio": -10,
+ "sticky": true
+ },
+ "em2": {
+ "prio": 100
+ }
+ }
+}</pre>
+
+ </div><div class="para">
+ To configure the interval between sending NS/NA packets, add or edit a section as follows:
+<pre class="screen">
+"link_watch": {
+ "name": "nsna_ping",
+ "interval": 200
+}</pre>
+ Value is positive number in milliseconds. It should be chosen in conjunction with the <code class="option">missed_max</code> option in order to determine the total time before a link is reported as down.
+ </div><div class="para">
+ To configure the maximum number of missed NS/NA reply packets to allow before reporting the link as down, add or edit a section as follows:
+<pre class="screen">
+"link_watch": {
+ "name": "nsna_ping",
+ "missed_max": 15
+}</pre>
+ Maximum number of missed NS/NA reply packets. If this number is exceeded, the link is reported as down. The <code class="option">missed_max</code> option is a limit value of the maximum allowed number of missed replies (ARP replies for example). It should be chosen in conjunction with the <code class="option">interval</code> option in order to determine the total time before a link is reported as down.
+ </div><div class="para">
+ To configure the host name that is resolved to the <code class="systemitem">IPv6</code> address target address for the NS/NA packets, add or edit a section as follows:
+<pre class="screen">
+"link_watch": {
+ "name": "nsna_ping",
+ "target_host": "MyStorage"
+}</pre>
+ The <span class="quote">“<span class="quote">target_host</span>”</span> option contains the host name to be converted to an <code class="systemitem">IPv6</code> address which will be used as the target address for the NS/NA packets. An <code class="systemitem">IPv6</code> address can be used in place of a host name.
+ </div><div class="para">
+ Please see the <code class="filename">teamd.conf(5)</code> man page for more information.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_the_LACP_Runner.html"><strong>Prev</strong>5.12.6. Configure the LACP (802.3ad) Runner</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_Port_Selection_Override.html"><strong>Next</strong>5.12.8. Configure Port Selection Override</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Network_Bonding-additional_resources.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Network_Bonding-additional_resources.html
new file mode 100644
index 0000000..b03336a
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Network_Bonding-additional_resources.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.6. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Bonding.html" title="Chapter 4. Configure Network Bonding" /><link rel="prev" href="sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli.html" title="4.5. Using the NetworkManager Command Line Tool, nmcli" /><link rel="next" href="sec-Configure_Network_Bonding_Online_Documentation.html" title="4.6.2. Online Documentation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"
><li class="previous"><a accesskey="p" href="sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_Network_Bonding_Online_Documentation.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_Network_Bonding-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.6. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding network bonding.
+ </div><div class="section" id="sec-Configure_Network_Bonding-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.6.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">nmcli(1)</code> man page — Describes <span class="application"><strong>NetworkManager</strong></span>'s command‐line tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nmcli-examples(5)</code> man page — Gives examples of <span class="application"><strong>nmcli</strong></span> commands.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nm-settings(5)</code> man page — Description of settings and parameters of <span class="application"><strong>NetworkManager</strong></span> connections.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli.html"><strong>Prev</strong>4.5. Using the NetworkManager Command Line Tool, ...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_Network_Bonding_Online_Documentation.html"><strong>Next</strong>4.6.2. Online Documentation</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Network_Bonding_Online_Documentation.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Network_Bonding_Online_Documentation.html
new file mode 100644
index 0000000..6a8ddba
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Network_Bonding_Online_Documentation.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.6.2. Online Documentation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_Network_Bonding-additional_resources.html" title="4.6. Additional Resources" /><link rel="prev" href="sec-Configure_Network_Bonding-additional_resources.html" title="4.6. Additional Resources" /><link rel="next" href="ch-Configure_Network_Teaming.html" title="Chapter 5. Configure Network Teaming" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-
Configure_Network_Bonding-additional_resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Configure_Network_Teaming.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_Network_Bonding_Online_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.6.2. Online Documentation</h3></div></div></div><div class="para">
+ <div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><em class="citetitle">Fedora 20 System Administrator's Guide</em></span></dt><dd><div class="para">
+ Explains the use of kernel module capabilities.
+ </div></dd></dl></div>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_Network_Bonding-additional_resources.html"><strong>Prev</strong>4.6. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Configure_Network_Teaming.html"><strong>Next</strong>Chapter 5. Configure Network Teaming</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Network_Teaming_Using_nmcli.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Network_Teaming_Using_nmcli.html
new file mode 100644
index 0000000..5e115a8
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Network_Teaming_Using_nmcli.html
@@ -0,0 +1,77 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.13. Configure Network Teaming Using nmcli</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Teaming.html" title="Chapter 5. Configure Network Teaming" /><link rel="prev" href="sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm.html" title="5.12.9. Configure BPF-based Tx Port Selectors" /><link rel="next" href="sec-Network_Teaming-additional_resources.html" title="5.14. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="prev
ious"><a accesskey="p" href="sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Teaming-additional_resources.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_Network_Teaming_Using_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.13. Configure Network Teaming Using nmcli</h2></div></div></div><div class="para">
+ To view the devices available on the system, issue the following command:
+<pre class="screen">~]$ <code class="command">nmcli connection show</code>
+NAME UUID TYPE DEVICE
+eth1 0e8185a1-f0fd-4802-99fb-bedbb31c689b 802-3-ethernet --
+eth0 dfe1f57b-419d-4d1c-aaf5-245deab82487 802-3-ethernet --</pre>
+
+ </div><div class="para">
+ To create a new team interface, with name <em class="replaceable"><code>team-ServerA</code></em>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection add type team ifname <em class="replaceable"><code>team-ServerA</code></em></code>
+Connection 'team-ServerA' (b954c62f-5fdd-4339-97b0-40efac734c50) successfully added.</pre>
+ <span class="application"><strong>NetworkManager</strong></span> will set its internal parameter <code class="option">connection.autoconnect</code> to <code class="literal">yes</code> and as no <code class="systemitem">IP</code> address was given <code class="option">ipv4.method</code> will be set to <code class="literal">auto</code>. <span class="application"><strong>NetworkManager</strong></span> will also write a configuration file to <code class="filename">/etc/sysconfig/network-scripts/ifcfg-team-ServerA</code> where the corresponding ONBOOT will be set to <code class="literal">yes</code> and BOOTPROTO will be set to <code class="literal">dhcp</code>.
+ </div><div class="para">
+ Note that manual changes to the ifcfg file will not be noticed by <span class="application"><strong>NetworkManger</strong></span> until the interface is next brought up. See <a class="xref" href="sec-Network_Configuration_Using_sysconfig_Files.html">Section 1.7, “Network Configuration Using sysconfig Files”</a> for more information on using configuration files.
+ </div><div class="para">
+ To view the other values assigned, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con show <em class="replaceable"><code>team-ServerA</code></em></code>
+connection.id: team-ServerA
+connection.uuid: b954c62f-5fdd-4339-97b0-40efac734c50
+connection.interface-name: ServerA
+connection.type: team
+connection.autoconnect: yes
+<em class="lineannotation"><span class="lineannotation">…</span></em>
+ipv4.method: auto
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em></pre>
+ As no JSON configuration file was specified the default values apply. See the <code class="filename">teamd.conf(5)</code> man page for more information on the team JSON parameters and their default values. Notice that the name was derived from the interface name by prepending the type. Alternatively, specify a name with the <code class="option">con-name</code> option as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection add type team con-name <em class="replaceable"><code>Team0</code></em> ifname <em class="replaceable"><code>ServerB</code></em></code>
+Connection 'Team0' (5f7160a1-09f6-4204-8ff0-6d96a91218a7) successfully added.</pre>
+ </div><div class="para">
+ To view the team interfaces just configured, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con show</code>
+NAME UUID TYPE DEVICE
+team-ServerA b954c62f-5fdd-4339-97b0-40efac734c50 team ServerA
+eth1 0e8185a1-f0fd-4802-99fb-bedbb31c689b 802-3-ethernet --
+eth0 dfe1f57b-419d-4d1c-aaf5-245deab82487 802-3-ethernet --
+Team0 5f7160a1-09f6-4204-8ff0-6d96a91218a7 team ServerB</pre>
+ </div><div class="para">
+ To change the name assigned to a team, issue a command in the following format: <pre class="synopsis"><code class="command">nmcli con mod <em class="replaceable"><code>old-team-name</code></em> connection.id <em class="replaceable"><code>new-team-name</code></em></code></pre>
+ </div><div class="para">
+ To load a team configuration file for a team that already exists, issue a command in the following format: <pre class="synopsis"><code class="command">nmcli connection modify <em class="replaceable"><code>team-name</code></em> team.config <em class="replaceable"><code>JSON-config</code></em></code></pre> You can specify the team configuration either as a JSON string or provide a file name containing the configuration. The file name can include the path. In both cases, what is stored in the <em class="parameter"><code>team.config</code></em> property is the JSON string. In the case of a JSON string, use single quotes around the string and paste the entire string to the command line.
+ </div><div class="para">
+ To review the <code class="literal">team.config</code> property, enter a command in the following format: <pre class="synopsis"><code class="command">nmcli con show <em class="replaceable"><code>team-name</code></em> | grep team.config</code></pre>
+ </div><div class="para">
+ To add an interface <em class="replaceable"><code>eth0</code></em> to <code class="literal">Team0</code>, with the name <em class="replaceable"><code>Team0-port1</code></em>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type team-slave con-name <em class="replaceable"><code>Team0-port1</code></em> ifname <em class="replaceable"><code>eth0</code></em> master <em class="replaceable"><code>Team0</code></em></code>
+Connection 'Team0-port1' (ccd87704-c866-459e-8fe7-01b06cf1cffc) successfully added.</pre>
+ Similarly, to add another interface, <em class="replaceable"><code>eth1</code></em>, with the name <em class="replaceable"><code>Team0-port2</code></em>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type team-slave con-name <em class="replaceable"><code>Team0-port2</code></em> ifname <em class="replaceable"><code>eth1</code></em> master <em class="replaceable"><code>Team0</code></em></code>
+Connection 'Team0-port2' (a89ccff8-8202-411e-8ca6-2953b7db52dd) successfully added.</pre>
+ At time of writing, <span class="application"><strong>nmcli</strong></span> only supports Ethernet ports.
+ </div><div class="para">
+ In order to bring up a team, the ports must be brought up first as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection up <em class="replaceable"><code>Team0-port1</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/2)</pre>
+
+<pre class="screen">~]$ <code class="command">nmcli connection up <em class="replaceable"><code>Team0-port2</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/3)</pre>
+ </div><div class="para">
+ You can verify that the team interface was brought up by the activation of the ports, as follows:
+<pre class="screen">~]$ <code class="command">ip link</code>
+3: Team0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT
+ link/ether 52:54:00:76:6f:f0 brd ff:ff:ff:ff:ff:f</pre>
+ Alternatively, issue a command to bring up the team as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection up <em class="replaceable"><code>Team0</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/4)</pre>
+
+ </div><div class="para">
+ See <a class="xref" href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html">Section 2.4, “Using the NetworkManager Command Line Tool, nmcli”</a> for an introduction to <span class="application"><strong>nmcli</strong></span>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm.html"><strong>Prev</strong>5.12.9. Configure BPF-based Tx Port Selectors</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Teaming-additional_resources.html"><strong>Next</strong>5.14. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Networking-additional_resources.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Networking-additional_resources.html
new file mode 100644
index 0000000..b8b97b4
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Networking-additional_resources.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Networking.html" title="Chapter 2. Configure Networking" /><link rel="prev" href="sec-Configuring_Static_Routes_Using_nmcli.html" title="2.4.3. Configuring Static Routes Using nmcli" /><link rel="next" href="sec-Configure_Networking_Online_Documentation.html" title="2.5.2. Online Documentation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Con
figuring_Static_Routes_Using_nmcli.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_Networking_Online_Documentation.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_Networking-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.5. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources relevant to this chapter.
+ </div><div class="section" id="sec-Configure_Networking-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.5.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">ip(8)</code> man page — Describes the <span class="application"><strong>ip</strong></span> utility's command syntax.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nmcli(1)</code> man page — Describes <span class="application"><strong>NetworkManager</strong></span>'s command‐line tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nmcli-examples(5)</code> man page — Gives examples of <span class="application"><strong>nmcli</strong></span> commands.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nm-settings(5)</code> man page — Describes <span class="application"><strong>NetworkManager</strong></span> properties and their settings.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Static_Routes_Using_nmcli.html"><strong>Prev</strong>2.4.3. Configuring Static Routes Using nmcli</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_Networking_Online_Documentation.html"><strong>Next</strong>2.5.2. Online Documentation</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Networking_Online_Documentation.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Networking_Online_Documentation.html
new file mode 100644
index 0000000..a0d7baa
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Networking_Online_Documentation.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.2. Online Documentation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_Networking-additional_resources.html" title="2.5. Additional Resources" /><link rel="prev" href="sec-Configure_Networking-additional_resources.html" title="2.5. Additional Resources" /><link rel="next" href="ch-Configure_Host_Names.html" title="Chapter 3. Configure Host Names" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_Networking
-additional_resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Configure_Host_Names.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_Networking_Online_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.5.2. Online Documentation</h3></div></div></div><div class="para">
+ <div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.rfc-editor.org/info/rfc1518"><em class="citetitle">RFC 1518</em></a> — Classless Inter-Domain Routing (CIDR)</span></dt><dd><div class="para">
+ Describes the CIDR Address Assignment and Aggregation Strategy, including variable-length subnetting.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.rfc-editor.org/info/rfc1918"><em class="citetitle">RFC 1918</em></a> — Address Allocation for Private Internets</span></dt><dd><div class="para">
+ Describes the range of <code class="systemitem">IPv4</code> addresses reserved for private use.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.rfc-editor.org/info/rfc3330"><em class="citetitle">RFC 3330</em></a> — Special-Use IPv4 Addresses</span></dt><dd><div class="para">
+ Describes the global and other specialized <code class="systemitem">IPv4</code> address blocks that have been assigned by the Internet Assigned Numbers Authority (IANA).
+ </div></dd></dl></div>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_Networking-additional_resources.html"><strong>Prev</strong>2.5. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Configure_Host_Names.html"><strong>Next</strong>Chapter 3. Configure Host Names</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Port_Selection_Override.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Port_Selection_Override.html
new file mode 100644
index 0000000..9a0df47
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_Port_Selection_Override.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.12.8. Configure Port Selection Override</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_teamd_Runners.html" title="5.12. Configure teamd Runners" /><link rel="prev" href="sec-Configure_Monitoring_of_the_Link_State.html" title="5.12.7. Configure Monitoring of the Link State" /><link rel="next" href="sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm.html" title="5.12.9. Configure BPF-based Tx Port Selectors" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><l
i class="previous"><a accesskey="p" href="sec-Configure_Monitoring_of_the_Link_State.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_Port_Selection_Override"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.8. Configure Port Selection Override</h3></div></div></div><div class="para">
+ The physical port which transmits a frame is normally selected by the kernel part of the team driver, and is not relevant to the user or system administrator. The output port is selected using the policies of the selected team mode (<code class="systemitem">teamd</code> runner). On occasion however, it is helpful to direct certain classes of outgoing traffic to certain physical interfaces to implement slightly more complex policies. By default the team driver is multiqueue aware and 16 queues are created when the driver initializes (see <a href="https://www.kernel.org/doc/Documentation/networking/multiqueue.txt">https://www.kernel.org/doc/Documentation/networking/multiqueue.txt</a> for details). If more or less queues are desired, the Netlink attribute <code class="command">tx_queues</code> can be used to change this value during the team driver instance creation.
+ </div><div class="para">
+ The queue ID for a port can be set by the port configuration option <code class="option">queue_id</code> as follows:
+<pre class="screen">
+{
+ "queue_id": 3
+}</pre>
+ These queue ID's can be used in conjunction with the <span class="application"><strong>tc</strong></span> utility to configure a multiqueue queue discipline and filters to bias certain traffic to be transmitted on certain port devices. For example, if using the above configuration and wanting to force all traffic bound to <code class="systemitem">192.168.1.100</code> to use <span class="interface">eth1</span> in the team as its output device, issue commands as <code class="systemitem">root</code> in the following format:
+<pre class="screen">~]# <code class="command">tc qdisc add dev team0 handle 1 root multiq</code>
+~]# <code class="command">tc filter add dev team0 protocol ip parent 1: prio 1 u32 match ip dst \</code>
+<code class="command"> 192.168.1.100 action skbedit queue_mapping 3</code></pre>
+ This mechanism of overriding runner selection logic in order to bind traffic to a specific port can be used with all runners.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_Monitoring_of_the_Link_State.html"><strong>Prev</strong>5.12.7. Configure Monitoring of the Link State</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_BPF-based_Tx_Port_Selectors_for_Hash_Computation_Algorithm.html"><strong>Next</strong>5.12.9. Configure BPF-based Tx Port Selectors</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_a_Network_Team_Using-the_Command_Line.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_a_Network_Team_Using-the_Command_Line.html
new file mode 100644
index 0000000..dc66935
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_a_Network_Team_Using-the_Command_Line.html
@@ -0,0 +1,113 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10. Configure a Network Team Using the Command Line</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Teaming.html" title="Chapter 5. Configure Network Teaming" /><link rel="prev" href="sec-Creating_a_Network_Team_Using_a_GUI.html" title="5.9. Creating a Network Team Using a GUI" /><link rel="next" href="sec-Creating_a_Network_Team_Using_ifcfg_Files.html" title="5.10.2. Creating a Network Team Using ifcfg Files" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a a
ccesskey="p" href="sec-Creating_a_Network_Team_Using_a_GUI.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Creating_a_Network_Team_Using_ifcfg_Files.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_a_Network_Team_Using-the_Command_Line"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.10. Configure a Network Team Using the Command Line</h2></div></div></div><div class="section" id="sec-Creating_a_Network_Team_Using_teamd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.1. Creating a Network Team Using teamd</h3></div></div></div><div class="para">
+ To create a network team, a JSON format configuration file is required for the virtual interface that will serve as the interface to the team of ports or links. A quick way is to copy the example configuration files and then edit them using an editor running with <code class="systemitem">root</code> privileges. To list the available example configurations, enter the following command:
+<pre class="screen">~]$ <code class="command">ls /usr/share/doc/teamd-*/example_configs/</code>
+activebackup_arp_ping_1.conf activebackup_multi_lw_1.conf loadbalance_2.conf
+activebackup_arp_ping_2.conf activebackup_nsna_ping_1.conf loadbalance_3.conf
+activebackup_ethtool_1.conf broadcast.conf random.conf
+activebackup_ethtool_2.conf lacp_1.conf roundrobin_2.conf
+activebackup_ethtool_3.conf loadbalance_1.conf roundrobin.conf</pre>
+ To view one of the included files, such as <code class="filename">activebackup_ethtool_1.conf</code>, enter the following command:
+<pre class="screen">~]$ <code class="command">cat /usr/share/doc/teamd-*/example_configs/activebackup_ethtool_1.conf</code>
+{
+ "device": "team0",
+ "runner": {"name": "activebackup"},
+ "link_watch": {"name": "ethtool"},
+ "ports": {
+ "eth1": {
+ "prio": -10,
+ "sticky": true
+ },
+ "eth2": {
+ "prio": 100
+ }
+ }
+}</pre>
+ Create a working configurations directory to store <code class="systemitem">teamd</code> configuration files. For example, as normal user, enter a command with the following format:
+<pre class="screen">~]$ <code class="command">mkdir ~/<em class="replaceable"><code>teamd_working_configs</code></em></code></pre>
+ Copy the file you have chosen to your working directory and edit it as necessary. As an example, you could use a command with the following format:
+<pre class="screen">~]$ <code class="command">cp /usr/share/doc/teamd-*/example_configs/activebackup_ethtool_1.conf \ ~/<em class="replaceable"><code>teamd_working_configs</code></em>/activebackup_ethtool_1.conf</code></pre>
+ To edit the file to suit your environment, for example to change the interfaces to be used as ports for the network team, open the file for editing as follows:
+<pre class="screen">~]$ <code class="command">vi ~/<em class="replaceable"><code>teamd_working_configs</code></em>/activebackup_ethtool_1.conf</code></pre>
+ Make any necessary changes and save the file. See the <code class="filename">vi(1)</code> man page for help on using the <span class="application"><strong>vi</strong></span> editor or use your preferred editor.
+ </div><div class="para">
+ Note that it is essential that the interfaces to be used as ports within the team must not be active, that is to say, they must be <span class="quote">“<span class="quote">down</span>”</span>, when adding them into a team device. To check their status, issue the following command:
+<pre class="screen">~]$ <code class="command">ip link show</code>
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
+ link/ether 52:54:00:d5:f7:d4 brd ff:ff:ff:ff:ff:ff
+3: em2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
+ link/ether 52:54:00:d8:04:70 brd ff:ff:ff:ff:ff:ff</pre>
+ In this example we see that both the interfaces we plan to use are <span class="quote">“<span class="quote">UP</span>”</span>.
+ </div><div class="para">
+ To take down an interface, issue a command as <code class="systemitem">root</code> in the following format:
+<pre class="screen">~]# <code class="command">ip link set down em1</code></pre>
+ Repeat for each interface as necessary.
+ </div><div class="para">
+ To create a team interface based on the configuration file, as <code class="systemitem">root</code> user, change to the working configurations directory (<em class="replaceable"><code>teamd_working_configs</code></em> in this example):
+<pre class="screen">~]# <code class="command">cd /home/<em class="replaceable"><code>user</code></em><em class="replaceable"><code>teamd_working_configs</code></em></code></pre>
+ Then issue a command in the following format:
+<pre class="screen">~]# <code class="command">teamd -g -f activebackup_ethtool_1.conf -d</code>
+Using team device "team0".
+Using PID file "/var/run/teamd/team0.pid"
+Using config file "/home/<em class="replaceable"><code>user</code></em>/teamd_working_configs/activebackup_ethtool_1.conf"</pre>
+ The <code class="option">-g</code> option is for debug messages, <code class="option">-f</code> option is to specify the configuration file to load, and the <code class="option">-d</code> option is to make the process run as a daemon after startup. See the <code class="filename">teamd(8)</code> man page for other options.
+ </div><div class="para">
+ To check the status of the team, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamdctl team0 state</code>
+setup:
+ runner: activebackup
+ports:
+ em1
+ link watches:
+ link summary: up
+ instance[link_watch_0]:
+ name: ethtool
+ link: up
+ em2
+ link watches:
+ link summary: up
+ instance[link_watch_0]:
+ name: ethtool
+ link: up
+runner:
+ active port: em1</pre>
+ </div><div class="para">
+ To apply an address to the network team interface, <span class="interface">team0</span>, issue a command as <code class="systemitem">root</code> in the following format:
+<pre class="screen">~]# <code class="command">ip addr add 192.168.23.2/24 dev team0</code></pre>
+
+ </div><div class="para">
+ To check the IP address of a team interface, issue a command as follows:
+<pre class="screen">~]$ <code class="command">ip addr show team0</code>
+4: team0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
+ link/ether 16:38:57:60:20:6f brd ff:ff:ff:ff:ff:ff
+ inet 192.168.23.2/24 scope global team0
+ valid_lft forever preferred_lft forever
+ inet6 2620:52:0:221d:1438:57ff:fe60:206f/64 scope global dynamic
+ valid_lft 2591880sec preferred_lft 604680sec
+ inet6 fe80::1438:57ff:fe60:206f/64 scope link
+ valid_lft forever preferred_lft forever</pre>
+
+ </div><div class="para">
+ To activate the team interface, or to bring it <span class="quote">“<span class="quote">up</span>”</span>, issue a command as <code class="systemitem">root</code> in the following format:
+<pre class="screen">~]# <code class="command">ip link set dev team0 up</code></pre>
+ </div><div class="para">
+ To temporarily deactivate the team interface, or to take it <span class="quote">“<span class="quote">down</span>”</span>, issue a command as <code class="systemitem">root</code> in the following format:
+<pre class="screen">~]# <code class="command">ip link set dev team0 down</code></pre>
+ </div><div class="para">
+ To terminate, or kill, an instance of the team daemon, as <code class="systemitem">root</code> user, issue a command in the following format:
+<pre class="screen">~]# <code class="command">teamd -t team0 -k</code></pre>
+ The <code class="option">-k</code> option is to specify that the instance of the daemon associated with the device <span class="interface">team0</span> is to be killed. See the <code class="filename">teamd(8)</code> man page for other options.
+ </div><div class="para">
+ For help on command-line options for <code class="systemitem">teamd</code>, issue the following command:
+<pre class="screen">~]$ <code class="command">teamd -h</code></pre>
+ In addition, see the <code class="filename">teamd(8)</code> man page.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Creating_a_Network_Team_Using_a_GUI.html"><strong>Prev</strong>5.9. Creating a Network Team Using a GUI</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Creating_a_Network_Team_Using_ifcfg_Files.html"><strong>Next</strong>5.10.2. Creating a Network Team Using ifcfg Files</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent.html
new file mode 100644
index 0000000..457e9c3
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.3.2. Configure dhcrelay as a DHCPv6 relay agent</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="dhcp-relay-agent.html" title="9.3. DHCP Relay Agent" /><link rel="prev" href="dhcp-relay-agent.html" title="9.3. DHCP Relay Agent" /><link rel="next" href="sec-Configuring_a_Multihomed_DHCP_Server.html" title="9.4. Configuring a Multihomed DHCP Server" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="dhcp-relay-agent.html"><strong>Prev</strong></a></li><li class="
next"><a accesskey="n" href="sec-Configuring_a_Multihomed_DHCP_Server.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.3.2. Configure dhcrelay as a DHCPv6 relay agent</h3></div></div></div><div class="para">
+ To run <span class="application"><strong>dhcrelay</strong></span> in <code class="systemitem">DHCPv6</code> mode add the <code class="option">-6</code> argument and specify the <span class="quote">“<span class="quote">lower interface</span>”</span> (on which queries will be received from clients or from other relay agents) and the <span class="quote">“<span class="quote">upper interface</span>”</span> (to which queries from clients and other relay agents should be forwarded). Copy <code class="filename">dhcrelay.service</code> to <code class="filename">dhcrelay6.service</code> and edit it as the <code class="systemitem">root</code> user:
+<pre class="screen">~]# <code class="command">cp /lib/systemd/system/dhcrelay.service /etc/systemd/system/dhcrelay6.service</code>
+~]# <code class="command">vi /etc/systemd/system/dhcrelay6.service</code></pre>
+ </div><div class="para">
+ Edit the <code class="option">ExecStart</code> option under section [Service] add <code class="option">-6</code> argument and add the <span class="quote">“<span class="quote">lower interface</span>”</span> and <span class="quote">“<span class="quote">upper interface</span>”</span> interface, for example: <pre class="synopsis">ExecStart=/usr/sbin/dhcrelay -d --no-pid -6 -l em1 -u em2</pre> For other options see the <code class="filename">dhcrelay(8)</code> man page.
+ </div><div class="para">
+ To activate the changes made, as the <code class="systemitem">root</code> user, restart the service:
+<pre class="screen">~]# <code class="command">systemctl --system daemon-reload</code>
+~]# <code class="command">systemctl restart dhcrelay6</code></pre>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="dhcp-relay-agent.html"><strong>Prev</strong>9.3. DHCP Relay Agent</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_a_Multihomed_DHCP_Server.html"><strong>Next</strong>9.4. Configuring a Multihomed DHCP Server</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_teamd_Runners.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_teamd_Runners.html
new file mode 100644
index 0000000..e8dc0e0
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_teamd_Runners.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.12. Configure teamd Runners</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Teaming.html" title="Chapter 5. Configure Network Teaming" /><link rel="prev" href="sec-View_the_Configuration_of_a_Port_in_a_Network_Team.html" title="5.11.4. View the Configuration of a Port in a Network Team" /><link rel="next" href="sec-Configure_the_random_Runner.html" title="5.12.2. Configure the random Runner" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"
><a accesskey="p" href="sec-View_the_Configuration_of_a_Port_in_a_Network_Team.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_the_random_Runner.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_teamd_Runners"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.12. Configure teamd Runners</h2></div></div></div><div class="para">
+ Runners are units of code which are compiled into the Team daemon when an instance of the daemon is created. For an introduction to the <code class="systemitem">teamd</code> runners, see <a class="xref" href="sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners.html">Section 5.4, “Understanding the Network Teaming Daemon and the "Runners"”</a>.
+ </div><div class="section" id="sec-Configure_the_broadcast_Runner"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.1. Configure the broadcast Runner</h3></div></div></div><div class="para">
+ To configure the broadcast runner, using an editor as <code class="systemitem">root</code>, add the following to the team JSON format configuration file:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {"name": "broadcast"},
+ "ports": {"em1": {}, "em2": {}}
+}</pre>
+
+ </div><div class="para">
+ Please see the <code class="filename">teamd.conf(5)</code> man page for more information.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-View_the_Configuration_of_a_Port_in_a_Network_Team.html"><strong>Prev</strong>5.11.4. View the Configuration of a Port in a Net...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_the_random_Runner.html"><strong>Next</strong>5.12.2. Configure the random Runner</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_the_LACP_Runner.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_the_LACP_Runner.html
new file mode 100644
index 0000000..5cbf866
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_the_LACP_Runner.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.12.6. Configure the LACP (802.3ad) Runner</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_teamd_Runners.html" title="5.12. Configure teamd Runners" /><link rel="prev" href="sec-Configure_the_loadbalance_Runner.html" title="5.12.5. Configure the loadbalance Runner" /><link rel="next" href="sec-Configure_Monitoring_of_the_Link_State.html" title="5.12.7. Configure Monitoring of the Link State" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href=
"sec-Configure_the_loadbalance_Runner.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_Monitoring_of_the_Link_State.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_the_LACP_Runner"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.6. Configure the LACP (802.3ad) Runner</h3></div></div></div><div class="para">
+ To configure the LACP runner using <span class="application"><strong>ethtool</strong></span> as a link watcher, using an editor as <code class="systemitem">root</code>, add the following to the team JSON format configuration file:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {
+ "name": "lacp",
+ "active": true,
+ "fast_rate": true,
+ "tx_hash": ["eth", "ipv4", "ipv6"]
+ },
+ "link_watch": {"name": "ethtool"},
+ "ports": {"em1": {}, "em2": {}}
+}</pre>
+ Configuration for connection to a <em class="firstterm">link aggregation control protocol</em> (<acronym class="acronym">LACP</acronym>) capable counterpart. The LACP runner should use <span class="application"><strong>ethtool</strong></span> to monitor the status of a link. It does not make sense to use any other link monitoring method besides the <span class="application"><strong>ethtool</strong></span> because, for example in the case of <span class="application"><strong>arp_ping</strong></span>, the link would never come up. The reason is that the link has to be established first and only after that can packets, ARP included, go through. Using <span class="application"><strong>ethtool</strong></span> prevents this because it monitors each link layer individually.
+ </div><div class="para">
+ Active load balancing is possible with this runner in the same way as it is done for the loadbalance runner. To enable active transmit (Tx) load balancing, add the following section:
+<pre class="screen">"tx_balancer": {
+ "name": "basic"
+}</pre>
+ </div><div class="para">
+ Please see the <code class="filename">teamd.conf(5)</code> man page for more information.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_the_loadbalance_Runner.html"><strong>Prev</strong>5.12.5. Configure the loadbalance Runner</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_Monitoring_of_the_Link_State.html"><strong>Next</strong>5.12.7. Configure Monitoring of the Link State</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_the_activebackup_Runner.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_the_activebackup_Runner.html
new file mode 100644
index 0000000..6be21fd
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_the_activebackup_Runner.html
@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.12.4. Configure the activebackup Runner</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_teamd_Runners.html" title="5.12. Configure teamd Runners" /><link rel="prev" href="sec-Configure_the_roundrobin_Runner.html" title="5.12.3. Configure the roundrobin Runner" /><link rel="next" href="sec-Configure_the_loadbalance_Runner.html" title="5.12.5. Configure the loadbalance Runner" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure
_the_roundrobin_Runner.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_the_loadbalance_Runner.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_the_activebackup_Runner"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.4. Configure the activebackup Runner</h3></div></div></div><div class="para">
+ The active backup runner can use all of the link-watchers to determine the status of links in a team. Any one of the following examples can be added to the team JSON format configuration file:
+ </div><div class="para">
+
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {
+ "name": "activebackup"
+ },
+ "link_watch": {
+ "name": "ethtool"
+ },
+ "ports": {
+ "em1": {
+ "prio": -10,
+ "sticky": true
+ },
+ "em2": {
+ "prio": 100
+ }
+ }
+}</pre>
+ This example configuration uses the active-backup runner with <span class="application"><strong>ethtool</strong></span> as the link watcher. Port <span class="interface">em2</span> has higher priority. The sticky flag ensures that if <span class="interface">em1</span> becomes active, it stays active as long as the link remains up.
+ </div><div class="para">
+
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {
+ "name": "activebackup"
+ },
+ "link_watch": {
+ "name": "ethtool"
+ },
+ "ports": {
+ "em1": {
+ "prio": -10,
+ "sticky": true,
+ "queue_id": 4
+ },
+ "em2": {
+ "prio": 100
+ }
+ }
+}</pre>
+ This example configuration adds a queue ID of <code class="literal">4</code>. It uses active-backup runner with <span class="application"><strong>ethtool</strong></span> as the link watcher. Port <span class="interface">em2</span> has higher priority. But the sticky flag ensures that if <span class="interface">em1</span> becomes active, it will stay active as long as the link remains up.
+ </div><div class="para">
+ To configure the activebackup runner using <span class="application"><strong>ethtool</strong></span> as the link watcher and applying a delay, using an editor as <code class="systemitem">root</code>, add the following to the team JSON format configuration file:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {
+ "name": "activebackup"
+ },
+ "link_watch": {
+ "name": "ethtool",
+ "delay_up": 2500,
+ "delay_down": 1000
+ },
+ "ports": {
+ "em1": {
+ "prio": -10,
+ "sticky": true
+ },
+ "em2": {
+ "prio": 100
+ }
+ }
+}</pre>
+ This example configuration uses the active-backup runner with <span class="application"><strong>ethtool</strong></span> as the link watcher. Port <span class="interface">em2</span> has higher priority. But the sticky flag ensures that if <span class="interface">em1</span> becomes active, it stays active while the link remains up. Link changes are not propagated to the runner immediately, but delays are applied.
+ </div><div class="para">
+ Please see the <code class="filename">teamd.conf(5)</code> man page for more information.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_the_roundrobin_Runner.html"><strong>Prev</strong>5.12.3. Configure the roundrobin Runner</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_the_loadbalance_Runner.html"><strong>Next</strong>5.12.5. Configure the loadbalance Runner</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_the_loadbalance_Runner.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_the_loadbalance_Runner.html
new file mode 100644
index 0000000..b275a24
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_the_loadbalance_Runner.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.12.5. Configure the loadbalance Runner</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_teamd_Runners.html" title="5.12. Configure teamd Runners" /><link rel="prev" href="sec-Configure_the_activebackup_Runner.html" title="5.12.4. Configure the activebackup Runner" /><link rel="next" href="sec-Configure_the_LACP_Runner.html" title="5.12.6. Configure the LACP (802.3ad) Runner" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure
_the_activebackup_Runner.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_the_LACP_Runner.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_the_loadbalance_Runner"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.5. Configure the loadbalance Runner</h3></div></div></div><div class="para">
+ This runner can be used for two types of load balancing, active and passive. In active mode, constant re-balancing of traffic is done by using statistics of recent traffic to share out traffic as evenly as possible. In static mode, streams of traffic are distributed randomly across the available links. This has a speed advantage due to lower processing overhead. In high volume traffic applications this is often preferred as traffic usually consists of multiple stream which will be distributed randomly between the available links, in his way load sharing is accomplished without intervention by <code class="systemitem">teamd</code>.
+ </div><div class="para">
+ To configure the loadbalance runner for passive transmit (Tx) load balancing, using an editor as <code class="systemitem">root</code>, add the following to the team JSON format configuration file:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {
+ "name": "loadbalance",
+ "tx_hash": ["eth", "ipv4", "ipv6"]
+ },
+ "ports": {"em1": {}, "em2": {}}
+}</pre>
+ Configuration for hash-based passive transmit (Tx) load balancing.
+ </div><div class="para">
+ To configure the loadbalance runner for active transmit (Tx) load balancing, using an editor as <code class="systemitem">root</code>, add the following to the team JSON format configuration file:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {
+ "name": "loadbalance",
+ "tx_hash": ["eth", "ipv4", "ipv6"],
+ "tx_balancer": {
+ "name": "basic"
+ }
+ },
+ "ports": {"em1": {}, "em2": {}}
+}</pre>
+ Configuration for active transmit (Tx) load balancing using basic load balancer.
+ </div><div class="para">
+ Please see the <code class="filename">teamd.conf(5)</code> man page for more information.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_the_activebackup_Runner.html"><strong>Prev</strong>5.12.4. Configure the activebackup Runner</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_the_LACP_Runner.html"><strong>Next</strong>5.12.6. Configure the LACP (802.3ad) Runner</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_the_random_Runner.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_the_random_Runner.html
new file mode 100644
index 0000000..d96c1a6
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_the_random_Runner.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.12.2. Configure the random Runner</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_teamd_Runners.html" title="5.12. Configure teamd Runners" /><link rel="prev" href="sec-Configure_teamd_Runners.html" title="5.12. Configure teamd Runners" /><link rel="next" href="sec-Configure_the_roundrobin_Runner.html" title="5.12.3. Configure the roundrobin Runner" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_teamd_Runners.html"
><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_the_roundrobin_Runner.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_the_random_Runner"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.2. Configure the random Runner</h3></div></div></div><div class="para">
+ The random runner behaves similarly to the roundrobin runner.
+ </div><div class="para">
+ To configure the random runner, using an editor as <code class="systemitem">root</code>, add the following to the team JSON format configuration file:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {"name": "random"},
+ "ports": {"em1": {}, "em2": {}}
+}</pre>
+
+ </div><div class="para">
+ Please see the <code class="filename">teamd.conf(5)</code> man page for more information.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_teamd_Runners.html"><strong>Prev</strong>5.12. Configure teamd Runners</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_the_roundrobin_Runner.html"><strong>Next</strong>5.12.3. Configure the roundrobin Runner</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_the_roundrobin_Runner.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_the_roundrobin_Runner.html
new file mode 100644
index 0000000..935130f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configure_the_roundrobin_Runner.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.12.3. Configure the roundrobin Runner</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_teamd_Runners.html" title="5.12. Configure teamd Runners" /><link rel="prev" href="sec-Configure_the_random_Runner.html" title="5.12.2. Configure the random Runner" /><link rel="next" href="sec-Configure_the_activebackup_Runner.html" title="5.12.4. Configure the activebackup Runner" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_the_r
andom_Runner.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_the_activebackup_Runner.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configure_the_roundrobin_Runner"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.12.3. Configure the roundrobin Runner</h3></div></div></div><div class="para">
+ To configure the roundrobin runner, using an editor as <code class="systemitem">root</code>, add the following to the team JSON format configuration file:
+<pre class="screen">
+{
+ "device": "team0",
+ "runner": {"name": "roundrobin"},
+ "ports": {"em1": {}, "em2": {}}
+}</pre>
+ A very basic configuration for roundrobin.
+ </div><div class="para">
+ Please see the <code class="filename">teamd.conf(5)</code> man page for more information.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_the_random_Runner.html"><strong>Prev</strong>5.12.2. Configure the random Runner</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_the_activebackup_Runner.html"><strong>Next</strong>5.12.4. Configure the activebackup Runner</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_Connection_Settings.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_Connection_Settings.html
new file mode 100644
index 0000000..953e306
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_Connection_Settings.html
@@ -0,0 +1,206 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.10. Configuring Connection Settings</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html" title="2.2. Using NetworkManager with the GNOME Graphical User Interface" /><link rel="prev" href="sec-Establishing_a_DSL_Connection.html" title="2.2.9. Establishing a DSL Connection" /><link rel="next" href="sec-Using_the_Command_Line_Interface.html" title="2.3. Using the Command Line Interface (CLI)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul c
lass="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_a_DSL_Connection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_the_Command_Line_Interface.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configuring_Connection_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.10. Configuring Connection Settings</h3></div></div></div><div class="section" id="sec-Configuring_802.1X_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.10.1. Configuring 802.1X Security</h4></div></div></div><div class="para">
+ 802.1X security is the name of the IEEE standard for <em class="firstterm">port-based Network Access Control</em> (<acronym class="acronym">PNAC</acronym>). It is also called <em class="firstterm">WPA Enterprise</em>. Simply put, 802.1X security is a way of controlling access to a <em class="firstterm">logical network</em> from a physical one. All clients who want to join the logical network must authenticate with the server (a router, for example) using the correct 802.1X authentication method.
+ </div><div class="para">
+ 802.1X security is most often associated with securing wireless networks (WLANs), but can also be used to prevent intruders with physical access to the network (LAN) from gaining entry. In the past, <code class="systemitem">DHCP</code> servers were configured not to lease <code class="systemitem">IP</code> addresses to unauthorized users, but for various reasons this practice is both impractical and insecure, and thus is no longer recommended. Instead, 802.1X security is used to ensure a logically-secure network through port-based authentication.
+ </div><div class="para">
+ 802.1X provides a framework for WLAN and LAN access control and serves as an envelope for carrying one of the Extensible Authentication Protocol (EAP) types. An EAP type is a protocol that defines how security is achieved on the network.
+ </div><div class="para">
+ You can configure 802.1X security for a wired or wireless connection type by opening the <span class="guilabel"><strong>Network</strong></span> window (see <a class="xref" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a>) and following the applicable procedure below. Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears. Proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#procedure-For_a_Wired_Connection">Procedure 2.9, “For a Wired Connection”</a> or <a class="xref" href="sec-Configuring_Connection_Settings.html#procedure-For_a_Wireless_Connection">Procedure 2.10, “For a Wi
reless Connection”</a>:
+ </div><div class="procedure" id="procedure-For_a_Wired_Connection"><h6>Procedure 2.9. For a Wired Connection</h6><ol class="1"><li class="step"><div class="para">
+ Select a <span class="guilabel"><strong>Wired</strong></span> network interface from the left-hand-side menu.
+ </div></li><li class="step"><div class="para">
+ Either click on <span class="guibutton"><strong>Add Profile</strong></span> to add a new network connection profile for which you want to configure 802.1X security, or select an existing connection profile and click the gear wheel icon.
+ </div></li><li class="step"><div class="para">
+ Then select <span class="guilabel"><strong>Security</strong></span> and set the symbolic power button to <span class="guilabel"><strong>ON</strong></span> to enable settings configuration.
+ </div></li><li class="step"><div class="para">
+ Proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_TLS_Transport_Layer_Security_Settings">Section 2.2.10.1.1, “Configuring TLS (Transport Layer Security) Settings”</a>
+ </div></li></ol></div><div class="procedure" id="procedure-For_a_Wireless_Connection"><h6>Procedure 2.10. For a Wireless Connection</h6><ol class="1"><li class="step"><div class="para">
+ Select a <span class="guilabel"><strong>Wireless</strong></span> network interface from the left-hand-side menu. If necessary, set the symbolic power button to <span class="guilabel"><strong>ON</strong></span> and check that your hardware switch is on.
+ </div></li><li class="step"><div class="para">
+ Either select the connection name of a new connection, or click the gear wheel icon of an existing connection profile, for which you want to configure 802.1X security. In the case of a new connection, complete any authentication steps to complete the connection and then click the gear wheel icon.
+ </div></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Security</strong></span>.
+ </div></li><li class="step"><div class="para">
+ From the drop-down menu select one of the following security methods: <span class="guimenuitem"><strong>LEAP</strong></span>, <span class="guimenuitem"><strong>Dynamic WEP (802.1X)</strong></span>, or <span class="guimenuitem"><strong>WPA & WPA2 Enterprise</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Refer to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_TLS_Transport_Layer_Security_Settings">Section 2.2.10.1.1, “Configuring TLS (Transport Layer Security) Settings”</a> for descriptions of which <em class="firstterm">extensible authentication protocol</em> (<acronym class="acronym">EAP</acronym>) types correspond to your selection in the <span class="guilabel"><strong>Security</strong></span> drop-down menu.
+ </div></li></ol></div><div class="section" id="sec-Configuring_TLS_Transport_Layer_Security_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.10.1.1. Configuring TLS (Transport Layer Security) Settings</h5></div></div></div><div class="para">
+ With Transport Layer Security, the client and server mutually authenticate using the TLS protocol. The server demonstrates that it holds a digital certificate, the client proves its own identity using its client-side certificate, and key information is exchanged. Once authentication is complete, the TLS tunnel is no longer used. Instead, the client and server use the exchanged keys to encrypt data using AES, TKIP or WEP.
+ </div><div class="para">
+ The fact that certificates must be distributed to all clients who want to authenticate means that the EAP-TLS authentication method is very strong, but also more complicated to set up. Using TLS security requires the overhead of a public key infrastructure (PKI) to manage certificates. The benefit of using TLS security is that a compromised password does not allow access to the (W)LAN: an intruder must also have access to the authenticating client's private key.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> does not determine the version of TLS supported. <span class="application"><strong>NetworkManager</strong></span> gathers the parameters entered by the user and passes them to the daemon, <span class="application"><strong>wpa_supplicant</strong></span>, that handles the procedure. It in turn uses OpenSSL to establish the TLS tunnel. OpenSSL itself negotiates the SSL/TLS protocol version. It uses the highest version both ends support.
+ </div><h6 id="Selecting_an_Authentication_Method">Selecting an Authentication Method</h6><div class="para">
+ Select from one of following authentication methods:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Select <span class="guilabel"><strong>TLS</strong></span> for <em class="firstterm">Transport Layer Security</em> and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_TLS_Settings">Section 2.2.10.1.2, “Configuring TLS Settings”</a>;
+ </div></li><li class="listitem"><div class="para">
+ Select <span class="guilabel"><strong>FAST</strong></span> for <em class="firstterm">Flexible Authentication via Secure Tunneling</em> and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_Tunneled_TLS_Settings">Section 2.2.10.1.4, “Configuring Tunneled TLS Settings”</a>;
+ </div></li><li class="listitem"><div class="para">
+ Select <span class="guilabel"><strong>Tunneled TLS</strong></span> for <em class="firstterm">Tunneled Transport Layer Security</em>, otherwise known as TTLS, or EAP-TTLS and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_Tunneled_TLS_Settings">Section 2.2.10.1.4, “Configuring Tunneled TLS Settings”</a>;
+ </div></li><li class="listitem"><div class="para">
+ Select <span class="guilabel"><strong>Protected EAP (PEAP)</strong></span> for <em class="firstterm">Protected Extensible Authentication Protocol</em> and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_Protected_EAP_PEAP_Settings">Section 2.2.10.1.5, “Configuring Protected EAP (PEAP) Settings”</a>.
+ </div></li></ul></div></div><div class="section" id="sec-Configuring_TLS_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.10.1.2. Configuring TLS Settings</h5></div></div></div><div class="para">
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Identity</strong></span> </span></dt><dd><div class="para">
+ Provide the identity of this server.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>User certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a personal X.509 certificate file encoded with <em class="firstterm">Distinguished Encoding Rules</em> (<acronym class="acronym">DER</acronym>) or <em class="firstterm">Privacy Enhanced Mail</em> (<acronym class="acronym">PEM</acronym>).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, an X.509 <em class="firstterm">certificate authority</em> certificate file encoded with <em class="firstterm">Distinguished Encoding Rules</em> (<acronym class="acronym">DER</acronym>) or <em class="firstterm">Privacy Enhanced Mail</em> (<acronym class="acronym">PEM</acronym>).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Private key</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a <em class="firstterm">private key</em> file encoded with <em class="firstterm">Distinguished Encoding Rules</em> (<acronym class="acronym">DER</acronym>), <em class="firstterm">Privacy Enhanced Mail</em> (<acronym class="acronym">PEM</acronym>), or the <em class="firstterm">Personal Information Exchange Syntax Standard</em> (<acronym class="acronym">PKCS #12</acronym>).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Private key password</strong></span> </span></dt><dd><div class="para">
+ Enter the password for the private key in the <span class="guilabel"><strong>Private key</strong></span> field. Select <span class="guilabel"><strong>Show password</strong></span> to make the password visible as you type it.
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_FAST_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.10.1.3. Configuring FAST Settings</h5></div></div></div><div class="para">
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Anonymous Identity</strong></span> </span></dt><dd><div class="para">
+ Provide the identity of this server.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>PAC provisioning</strong></span> </span></dt><dd><div class="para">
+ Select the check box to enable and then select from <span class="guimenu"><strong>Anonymous</strong></span>, <span class="guimenu"><strong>Authenticated</strong></span>, and <span class="guimenu"><strong>Both</strong></span>.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>PAC file</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a <em class="firstterm">protected access credential</em> (<acronym class="acronym">PAC</acronym>) file.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Inner authentication</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>GTC</strong></span> — Generic Token Card.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MSCHAPv2</strong></span> — Microsoft Challenge Handshake Authentication Protocol version 2.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the user name to be used in the authentication process.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password to be used in the authentication process.
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_Tunneled_TLS_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.10.1.4. Configuring Tunneled TLS Settings</h5></div></div></div><div class="para">
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Anonymous identity</strong></span> </span></dt><dd><div class="para">
+ This value is used as the unencrypted identity.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a Certificate Authority's certificate.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Inner authentication</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>PAP</strong></span> — Password Authentication Protocol.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MSCHAP</strong></span> — Challenge Handshake Authentication Protocol.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MSCHAPv2</strong></span> — Microsoft Challenge Handshake Authentication Protocol version 2.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>CHAP</strong></span> — Challenge Handshake Authentication Protocol.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the user name to be used in the authentication process.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password to be used in the authentication process.
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_Protected_EAP_PEAP_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.10.1.5. Configuring Protected EAP (PEAP) Settings</h5></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Anonymous Identity</strong></span> </span></dt><dd><div class="para">
+ This value is used as the unencrypted identity.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ Click to browse for, and select, a Certificate Authority's certificate.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>PEAP version</strong></span> </span></dt><dd><div class="para">
+ The version of Protected EAP to use. Automatic, 0 or 1.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Inner authentication</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>MSCHAPv2</strong></span> — Microsoft Challenge Handshake Authentication Protocol version 2.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MD5</strong></span> — Message Digest 5, a cryptographic hash function.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>GTC</strong></span> — Generic Token Card.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the user name to be used in the authentication process.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password to be used in the authentication process.
+ </div></dd></dl></div></div></div><div class="section" id="sec-Configuring_Wi-Fi_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.10.2. Configuring Wi-Fi Security</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Security</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>None</strong></span> — Do not encrypt the Wi-Fi connection.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WEP 40/128-bit Key</strong></span> — Wired Equivalent Privacy (WEP), from the IEEE 802.11 standard. Uses a single pre-shared key (PSK).
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WEP 128-bit Passphrase</strong></span> — An MD5 hash of the passphrase will be used to derive a WEP key.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>LEAP</strong></span> — Lightweight Extensible Authentication Protocol, from Cisco Systems.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Dynamic WEP (802.1X)</strong></span> — WEP keys are changed dynamically. Use with <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_TLS_Transport_Layer_Security_Settings">Section 2.2.10.1.1, “Configuring TLS (Transport Layer Security) Settings”</a>
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WPA & WPA2 Personal</strong></span> — Wi-Fi Protected Access (WPA), from the draft IEEE 802.11i standard. A replacement for WEP. Wi-Fi Protected Access II (WPA2), from the 802.11i-2004 standard. Personal mode uses a pre-shared key (WPA-PSK).
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WPA & WPA2 Enterprise</strong></span> — WPA for use with a RADIUS authentication server to provide IEEE 802.1X network access control. Use with <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_TLS_Transport_Layer_Security_Settings">Section 2.2.10.1.1, “Configuring TLS (Transport Layer Security) Settings”</a>
+ </div></dd><dt class="varlistentry"><span class="term">Password</span></dt><dd><div class="para">
+ Enter the password to be used in the authentication process.
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_PPP_Point-to-Point_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.10.3. Configuring PPP (Point-to-Point) Settings</h4></div></div></div><div class="para">
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Configure Methods</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Use point-to-point encryption (MPPE)</strong></span> </span></dt><dd><div class="para">
+ Microsoft Point-To-Point Encryption protocol (<a href="http://www.rfc-editor.org/info/rfc3078"><em class="citetitle">RFC 3078</em></a>).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Allow BSD data compression</strong></span> </span></dt><dd><div class="para">
+ PPP BSD Compression Protocol (<a href="http://www.rfc-editor.org/info/rfc1977"><em class="citetitle">RFC 1977</em></a>).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Allow Deflate data compression</strong></span> </span></dt><dd><div class="para">
+ PPP Deflate Protocol (<a href="http://www.rfc-editor.org/info/rfc1979"><em class="citetitle">RFC 1979</em></a>).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Use TCP header compression</strong></span> </span></dt><dd><div class="para">
+ Compressing TCP/IP Headers for Low-Speed Serial Links (<a href="http://www.rfc-editor.org/info/rfc1144"><em class="citetitle">RFC 1144</em></a>).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Send PPP echo packets</strong></span> </span></dt><dd><div class="para">
+ LCP Echo-Request and Echo-Reply Codes for loopback tests (<a href="http://www.rfc-editor.org/info/rfc1661"><em class="citetitle">RFC 1661</em></a>).
+ </div></dd></dl></div></div><div class="section" id="sec-Configuring_IPv4_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.10.4. Configuring IPv4 Settings</h4></div></div></div><div class="para">
+ The <span class="guilabel"><strong>IPv4 Settings</strong></span> tab allows you to configure the method used to connect to a network, to enter <code class="systemitem">IP</code> address, route, and <code class="systemitem">DNS</code> information as required. The <span class="guilabel"><strong>IPv4 Settings</strong></span> tab is available when you create and modify one of the following connection types: wired, wireless, mobile broadband, VPN or DSL. If you need to configure <code class="systemitem">IPv6</code> addresses, see <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv6_Settings">Section 2.2.10.5, “Configuring IPv6 Settings”</a>. If you need to configure static routes, click the <span class="guibutton"><strong>Routes</strong></span> button and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_Routes">Section 2.2.10.6, “Configuring Routes”</a>.
+ </div><div class="para">
+ If you are using <code class="systemitem">DHCP</code> to obtain a dynamic <code class="systemitem">IP</code> address from a <code class="systemitem">DHCP</code> server, you can simply set <span class="guilabel"><strong>Method</strong></span> to <span class="guimenuitem"><strong>Automatic (DHCP)</strong></span>.
+ </div><h5 id="bh-Setting_the_Method">Setting the Method</h5><div class="variablelist" id="varlist-Available_IPv4_Methods_by_Connection_Type"><h6>Available IPv4 Methods by Connection Type</h6><div class="para">
+ When you click the <span class="guilabel"><strong>Method</strong></span> drop-down menu, depending on the type of connection you are configuring, you are able to select one of the following <code class="systemitem">IPv4</code> connection methods. All of the methods are listed here according to which connection type, or types, they are associated with:
+ </div><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Method</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (DHCP)</strong></span> — Choose this option if the network you are connecting to uses a <code class="systemitem">DHCP</code> server to assign <code class="systemitem">IP</code> addresses. You do not need to fill in the <span class="guilabel"><strong>DHCP client ID</strong></span> field.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (DHCP) addresses only</strong></span> — Choose this option if the network you are connecting to uses a <code class="systemitem">DHCP</code> server to assign <code class="systemitem">IP</code> addresses but you want to assign <code class="systemitem">DNS</code> servers manually.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Link-Local Only</strong></span> — Choose this option if the network you are connecting to does not have a <code class="systemitem">DHCP</code> server and you do not want to assign <code class="systemitem">IP</code> addresses manually. Random addresses will be assigned as per <a href="http://www.rfc-editor.org/info/rfc3927"><em class="citetitle">RFC 3927</em></a> with prefix <code class="systemitem">169.254/16</code>.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Shared to other computers</strong></span> — Choose this option if the interface you are configuring is for sharing an Internet or WAN connection. The interface is assigned an address in the <code class="systemitem">10.42.x.1/24</code> range, a <code class="systemitem">DHCP</code> server and <code class="systemitem">DNS</code> server are started, and the interface is connected to the default network connection on the system with <em class="firstterm">network address translation</em> (<acronym class="acronym">NAT</acronym>).
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Disabled</strong></span> — <code class="systemitem">IPv4</code> is disabled for this connection.
+ </div></dd><dt class="varlistentry"><span class="term">Wired, Wireless and DSL Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Manual</strong></span> — Choose this option if you want to assign <code class="systemitem">IP</code> addresses manually.
+ </div></dd><dt class="varlistentry"><span class="term">Mobile Broadband Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPP)</strong></span> — Choose this option if the network you are connecting to assigns your <code class="systemitem">IP</code> address and <code class="systemitem">DNS</code> servers automatically.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPP) addresses only</strong></span> — Choose this option if the network you are connecting to assigns your <code class="systemitem">IP</code> address automatically, but you want to manually specify <code class="systemitem">DNS</code> servers.
+ </div></dd><dt class="varlistentry"><span class="term">VPN Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (VPN)</strong></span> — Choose this option if the network you are connecting to assigns your <code class="systemitem">IP</code> address and <code class="systemitem">DNS</code> servers automatically.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (VPN) addresses only</strong></span> — Choose this option if the network you are connecting to assigns your <code class="systemitem">IP</code> address automatically, but you want to manually specify <code class="systemitem">DNS</code> servers.
+ </div></dd><dt class="varlistentry"><span class="term">DSL Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPPoE)</strong></span> — Choose this option if the network you are connecting to assigns your <code class="systemitem">IP</code> address and <code class="systemitem">DNS</code> servers automatically.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPPoE) addresses only</strong></span> — Choose this option if the network you are connecting to assigns your <code class="systemitem">IP</code> address automatically, but you want to manually specify <code class="systemitem">DNS</code> servers.
+ </div></dd></dl></div><div class="para">
+ For information on configuring static routes for the network connection, go to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_Routes">Section 2.2.10.6, “Configuring Routes”</a>.
+ </div></div><div class="section" id="sec-Configuring_IPv6_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.10.5. Configuring IPv6 Settings</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Method</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Ignore</strong></span> — Choose this option if you want to ignore <code class="systemitem">IPv6</code> settings for this connection.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic</strong></span> — Choose this option to use <em class="firstterm">SLAAC</em> to create an automatic, stateless configuration based on the hardware address and <em class="firstterm">router advertisements</em> (RA).
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic, addresses only</strong></span> — Choose this option if the network you are connecting to uses <em class="firstterm">router advertisements</em> (RA) to create an automatic, stateless configuration, but you want to assign <code class="systemitem">DNS</code> servers manually.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic, DHCP only</strong></span> — Choose this option to not use RA, but request information from <code class="systemitem">DHCPv6</code> directly to create a stateful configuration.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Manual</strong></span> — Choose this option if you want to assign <code class="systemitem">IP</code> addresses manually.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Link-Local Only</strong></span> — Choose this option if the network you are connecting to does not have a <code class="systemitem">DHCP</code> server and you do not want to assign <code class="systemitem">IP</code> addresses manually. Random addresses will be assigned as per <a href="http://www.rfc-editor.org/info/rfc4862"><em class="citetitle">RFC 4862</em></a> with prefix <code class="systemitem">FE80::0</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Addresses</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>DNS servers</strong></span> — Enter a comma separated list of <code class="systemitem">DNS</code> servers.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Search domains</strong></span> — Enter a comma separated list of domain controllers.
+ </div></dd></dl></div><div class="para">
+ For information on configuring static routes for the network connection, go to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_Routes">Section 2.2.10.6, “Configuring Routes”</a>.
+ </div></div><div class="section" id="sec-Configuring_Routes"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.10.6. Configuring Routes</h4></div></div></div><div class="para">
+ A host's routing table will be automatically populated with routes to directly connected networks. The routes are learned by examining the network interfaces when they are <span class="quote">“<span class="quote">up</span>”</span>. This section describes entering static routes to networks or hosts which can be reached by traversing an intermediate network or connection, such as a VPN tunnel or leased line. In order to reach a remote network or host, the system is given the address of a gateway to which traffic should be sent.
+ </div><div class="para">
+ When a host's interface is configured by <code class="systemitem">DHCP</code>, an address of a gateway that leads to an upstream network or the Internet is usually assigned. This gateway is usually referred to as the default gateway as it is the gateway to use if no better route is known to the system (and present in the routing table). Network administrators often use the first or last host <code class="systemitem">IP</code> address in the network as the gateway address; for example, <code class="systemitem">192.168.10.1</code> or <code class="systemitem">192.168.10.254</code>. Not to be confused by the address which represents the network itself; in this example, <code class="systemitem">192.168.10.0</code>, or the subnet's broadcast address; in this example <code class="systemitem">192.168.10.255</code>.
+ </div><h5 id="Configuring_Static_Routes">Configuring Static Routes</h5><div class="para">
+ To set a static route, open the <span class="guimenu"><strong>IPv4</strong></span> or <span class="guimenu"><strong>IPv6</strong></span> settings window for the connection you want to configure. See <a class="xref" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for instructions on how to do that.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Routes</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Address</strong></span> — Enter the <code class="systemitem">IP</code> address of a remote network, sub-net, or host.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Netmask</strong></span> — The netmask or prefix length of the <code class="systemitem">IP</code> address entered above.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Gateway</strong></span> — The <code class="systemitem">IP</code> address of the gateway leading to the remote network, sub-net, or host entered above.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Metric</strong></span> — A network cost, a preference value to give to this route. Lower values will be preferred over higher values.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guibutton"><strong>Automatic</strong></span> </span></dt><dd><div class="para">
+ When Automatic is <span class="guilabel"><strong>ON</strong></span>, routes from <code class="systemitem">RA</code> or <code class="systemitem">DHCP</code> are used, but you can also add additional static routes. When <span class="guilabel"><strong>OFF</strong></span>, only static routes you define are used.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Use this connection only for resources on its network</strong></span> </span></dt><dd><div class="para">
+ Select this check box to prevent the connection from becoming the default route. Typical examples are where a connection is a VPN tunnel or a leased line to a head office and you do not want any Internet-bound traffic to pass over the connection. Selecting this option means that only traffic specifically destined for routes learned automatically over the connection or entered here manually will be routed over the connection.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_a_DSL_Connection.html"><strong>Prev</strong>2.2.9. Establishing a DSL Connection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_the_Command_Line_Interface.html"><strong>Next</strong>2.3. Using the Command Line Interface (CLI)</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_Host_Names_Using_nmcli.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_Host_Names_Using_nmcli.html
new file mode 100644
index 0000000..143101c
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_Host_Names_Using_nmcli.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.3. Configuring Host Names Using nmcli</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Host_Names.html" title="Chapter 3. Configure Host Names" /><link rel="prev" href="sec_Changing_Host_Names_Remotely.html" title="3.2.5. Changing Host Names Remotely" /><link rel="next" href="sec-additional_resources.html" title="3.4. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec_Changing_Host_Names_Remotely.html"><strong>P
rev</strong></a></li><li class="next"><a accesskey="n" href="sec-additional_resources.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configuring_Host_Names_Using_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.3. Configuring Host Names Using nmcli</h2></div></div></div><div class="para">
+ The <span class="application"><strong>NetworkManager</strong></span> tool <span class="application"><strong>nmcli</strong></span> can be used to query and set the static host name in the <code class="filename">/etc/hostname</code> file. Note that at time of writing, changing the host name in this way will not be noticed by <span class="application"><strong>hostnamectl</strong></span>.
+ </div><div class="para">
+ To query the static host name, issue the following command:
+<pre class="screen">~]$ <code class="command">nmcli general hostname</code></pre>
+ To set the static host name to <em class="replaceable"><code>my-server</code></em>, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">nmcli general hostname <em class="replaceable"><code>my-server</code></em></code></pre>
+ To force <span class="application"><strong>hostnamectl</strong></span> to notice the change in the static host name, restart <code class="systemitem">hostnamed</code> as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl restart systemd-hostnamed</code></pre>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec_Changing_Host_Names_Remotely.html"><strong>Prev</strong>3.2.5. Changing Host Names Remotely</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-additional_resources.html"><strong>Next</strong>3.4. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_IPv6_Tokenized_Interface_Identifiers.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_IPv6_Tokenized_Interface_Identifiers.html
new file mode 100644
index 0000000..9d99179
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_IPv6_Tokenized_Interface_Identifiers.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.5. Configuring IPv6 Tokenized Interface Identifiers</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Using_the_Command_Line_Interface.html" title="2.3. Using the Command Line Interface (CLI)" /><link rel="prev" href="sec-Configuring_Static_Routes_in_ifcfg_files.html" title="2.3.4. Configuring Static Routes in ifcfg files" /><link rel="next" href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html" title="2.4. Using the NetworkManager Command Line Tool, nmcli" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul cl
ass="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Static_Routes_in_ifcfg_files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configuring_IPv6_Tokenized_Interface_Identifiers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.5. Configuring IPv6 Tokenized Interface Identifiers</h3></div></div></div><div class="para">
+ In a network, servers are generally given static addresses and these are usually configured manually to avoid relying on a <code class="systemitem">DHCP</code> server which may fail or run out of addresses. The <code class="systemitem">IPv6</code> protocol introduced <em class="firstterm">Stateless Address Autoconfiguration</em> (<acronym class="acronym">SLAAC</acronym>) which enables clients to assign themselves an address without relying on a <code class="systemitem">DHCPv6</code> server. SLAAC derives the <code class="systemitem">IPv6</code> address based on the interface hardware, therefore it should not be used for servers in case the hardware is changed and the associated SLAAC generated address changes with it. In an <code class="systemitem">IPv6</code> environment, if the network prefix is changed, or the system is moved to a new location, any manually configured static addresses would have to be edited due to the changed prefix.
+ </div><div class="para">
+ To address these problems, the IETF draft <a href="https://tools.ietf.org/id/draft-chown-6man-tokenised-ipv6-identifiers-02.txt"><em class="citetitle">Tokenised IPv6 Identifiers</em></a> has been implemented in the kernel together with corresponding additions to the <code class="command">ip</code> utility. This enables the lower 64 bit interface identifier part of the <code class="systemitem">IPv6</code> address to be based on a token, supplied by the administrator, leaving the network prefix, the higher 64 bits, to be obtained from <em class="firstterm">router advertisements</em> (<acronym class="acronym">RA</acronym>). This means that if the network interface hardware is changed, the lower 64 bits of the address will not change, and if the system is moved to another network, the network prefix will be obtained from router advertisements automatically, thus no manual editing is required.
+ </div><div class="para">
+ To configure an interface to use a tokenized <code class="systemitem">IPv6</code> identifier, issue a command in the following format as <code class="systemitem">root</code> user:
+<pre class="screen">~]# <code class="command">ip token set ::1a:2b:3c:4d/64 dev eth4</code></pre>
+ Where <code class="literal">::1a:2b:3c:4d/64</code> is the token to be used. This setting is not persistent. To make it persistent, add the command to an init script. See <a class="xref" href="sec-Network_Configuration_Using_sysconfig_Files.html">Section 1.7, “Network Configuration Using sysconfig Files”</a> for information on network scripts.
+ </div><div class="para">
+ Using a memorable token is possible, but is limited to the range of valid hexadecimal digits. For example, for a <code class="systemitem">DNS</code> server, which traditionally uses port <code class="literal">53</code>, a token of <code class="literal">::53/64</code> could be used.
+ </div><div class="para">
+ To view all the configured <code class="systemitem">IPv6</code> tokens, issue the following command:
+<pre class="screen">~]$ <code class="command">ip token</code>
+ token :: dev eth0
+ token :: dev eth1
+ token :: dev eth2
+ token :: dev eth3
+ token ::1a:2b:3c:4d dev eth4</pre>
+
+ </div><div class="para">
+ To view the configured <code class="systemitem">IPv6</code> token for a specific interface, issue the following command:
+<pre class="screen">~]$ <code class="command">ip token get dev eth4</code>
+ token ::1a:2b:3c:4d dev eth4</pre>
+
+ </div><div class="para">
+ Note that adding a token to an interface will replace a previously allocated token, and in turn invalidate the address derived from it. Supplying a new token causes a new address to be generated and applied, but this process will leave any other addresses unchanged. In other words, a new tokenized identifier only replaces a previously existing tokenized identifier, not any other <code class="systemitem">IP</code> address.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Take care not to add the same token to more than one system or interface. The duplicate address detection (<acronym class="acronym">DAD</acronym>) mechanism will remove the duplicate address from the interface but it cannot change the configuration. Once a token is set, it cannot be cleared or reset, except by rebooting the machine.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Static_Routes_in_ifcfg_files.html"><strong>Prev</strong>2.3.4. Configuring Static Routes in ifcfg files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html"><strong>Next</strong>2.4. Using the NetworkManager Command Line Tool, ...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_New_and_Editing_Existing_Connections.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_New_and_Editing_Existing_Connections.html
new file mode 100644
index 0000000..40d849f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_New_and_Editing_Existing_Connections.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.2. Configuring New and Editing Existing Connections</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html" title="2.2. Using NetworkManager with the GNOME Graphical User Interface" /><link rel="prev" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html" title="2.2. Using NetworkManager with the GNOME Graphical User Interface" /><link rel="next" href="sec-Connecting_to_a_Network_Automatically.html" title="2.2.3. Connecting to a Network Automatically" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Conten
t/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Connecting_to_a_Network_Automatically.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configuring_New_and_Editing_Existing_Connections"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.2. Configuring New and Editing Existing Connections</h3></div></div></div><div class="para">
+ The <span class="guilabel"><strong>Network</strong></span> settings window shows the connection status, its type and interface, its <code class="systemitem">IP</code> address and routing details, and so on.
+ </div><div class="figure" id="exam-Configuring_New_and_Editing_Existing_Connections_Network-Settings-Window"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network-Wired_Gnome3.png"><img src="images/Network-Wired_Gnome3.png" alt="Configure Networks Using the Network Settings Window" /><div class="longdesc"><div class="para">
+ A screen shot of the GNOME control-center Network Settings window. The menu is on the left, the connection status button on the right.
+ </div></div></div></div><h6>Figure 2.1. Configure Networks Using the Network Settings Window</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>Network</strong></span> settings window has a menu on the left-hand side showing the available network devices or interfaces. This includes software interfaces such as for VLANs, bridges, bonds, and teams. On the right-hand side, the <em class="firstterm">connection profiles</em> are shown for the selected network device or interface. A profile is a named collection of settings that can be applied to an interface. Below that is a plus and a minus button for adding and deleting new network connections, and on the right a gear wheel icon will appear for editing the connection details of the selected network device or VPN connection. To add a new connection, click the plus symbol to open the <span class="guilabel"><strong>Add Network Connection</strong></span> window and proceed to <a class="xref" href="sec-Configuring_New_and_Editing_Existing_Connections.html#sec-Configuring_a_New_Connection">Section 2.2.2.1, “Configuring a New Connect
ion”</a>.
+ </div><h4 id="bh-Editing_an_Existing_Connection">Editing an Existing Connection</h4><div class="para">
+ Clicking on the gear wheel icon of an existing connection profile in the <span class="guilabel"><strong>Network</strong></span> settings window opens the <span class="guilabel"><strong>Network</strong></span> details window, from where you can perform most network configuration tasks such as <code class="systemitem">IP</code> addressing, <code class="systemitem">DNS</code>, and routing configuration.
+ </div><div class="figure" id="exam-Configuring_New_and_Editing_Existing_Connections_Network-Details-Window"><div class="figure-contents"><div class="mediaobject" id="mediaobj-Network-Details-Wired_Gnome3.png"><img src="images/Network-Details-Wired_Gnome3.png" alt="Configure Networks Using the Network Connection Details Window" /><div class="longdesc"><div class="para">
+ A screen shot of GNOME's Network Interface Detail window. The menu is on the left.
+ </div></div></div></div><h6>Figure 2.2. Configure Networks Using the Network Connection Details Window</h6></div><br class="figure-break" /><div class="section" id="sec-Configuring_a_New_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.2.1. Configuring a New Connection</h4></div></div></div><div class="para">
+ In the <span class="guilabel"><strong>Network</strong></span> settings window, click the plus sign below the menu to open the <span class="guilabel"><strong>Add Network Connection</strong></span> window. This displays a list of connection types that can be added.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ VPN connections, click the <span class="guilabel"><strong>VPN</strong></span> entry and proceed to <a class="xref" href="sec-Establishing_a_VPN_Connection.html">Section 2.2.7, “Establishing a VPN Connection”</a>;
+ </div></li><li class="listitem"><div class="para">
+ Bond connections, click the <span class="guilabel"><strong>Bond</strong></span> entry and proceed to <a class="xref" href="sec-Creating_a_Bond_Connection_Using_a_GUI.html#sec-Establishing_a_Bond_Connection">Section 4.2.1, “Establishing a Bond Connection”</a>;
+ </div></li><li class="listitem"><div class="para">
+ Bridge connections, click the <span class="guilabel"><strong>Bridge</strong></span> entry and proceed to <a class="xref" href="ch-Configure_Network_Bridging.html#sec-Establishing_a_Bridge_Connection">Section 6.1.1, “Establishing a Bridge Connection”</a>;
+ </div></li><li class="listitem"><div class="para">
+ VLAN connections, click the <span class="guilabel"><strong>VLAN</strong></span> entry and proceed to <a class="xref" href="sec-Configure_802_1Q_VLAN_Tagging_Using_a_GUI.html#sec-Establishing_a_VLAN_Connection">Section 7.2.1, “Establishing a VLAN Connection”</a>;or,
+ </div></li><li class="listitem"><div class="para">
+ Team connections, click the <span class="guilabel"><strong>Team</strong></span> entry and proceed to <a class="xref" href="sec-Creating_a_Network_Team_Using_a_GUI.html">Section 5.9, “Creating a Network Team Using a GUI”</a>.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html"><strong>Prev</strong>2.2. Using NetworkManager with the GNOME Graphica...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Connecting_to_a_Network_Automatically.html"><strong>Next</strong>2.2.3. Connecting to a Network Automatically</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_Options_of_a_Team_Using_teamnl.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_Options_of_a_Team_Using_teamnl.html
new file mode 100644
index 0000000..061bb56
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_Options_of_a_Team_Using_teamnl.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.5. Configuring Options of a Team Using teamnl</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_a_Network_Team_Using-the_Command_Line.html" title="5.10. Configure a Network Team Using the Command Line" /><link rel="prev" href="sec-Listing_the_ports_of_a_Team_Using_teamnl.html" title="5.10.4. Listing the ports of a Team Using teamnl" /><link rel="next" href="sec-Add_an_address_to_a_Network_Team_Using_iputils.html" title="5.10.6. Add an Address to a Network Team Using iputils" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentatio
n Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Listing_the_ports_of_a_Team_Using_teamnl.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Add_an_address_to_a_Network_Team_Using_iputils.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configuring_Options_of_a_Team_Using_teamnl"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.5. Configuring Options of a Team Using teamnl</h3></div></div></div><div class="para">
+ To view or list all currently available options, using the <span class="application"><strong>teamnl</strong></span> utility, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamnl team0 options</code></pre>
+ To configure a team to use active backup mode, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamnl team0 setoption mode activebackup</code></pre>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Listing_the_ports_of_a_Team_Using_teamnl.html"><strong>Prev</strong>5.10.4. Listing the ports of a Team Using teamnl</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Add_an_address_to_a_Network_Team_Using_iputils.html"><strong>Next</strong>5.10.6. Add an Address to a Network Team Using ip...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_Static_Routes_Using_nmcli.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_Static_Routes_Using_nmcli.html
new file mode 100644
index 0000000..e79f5a7
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_Static_Routes_Using_nmcli.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.3. Configuring Static Routes Using nmcli</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html" title="2.4. Using the NetworkManager Command Line Tool, nmcli" /><link rel="prev" href="sec-Connecting_to_a_Network_Using_nmcli.html" title="2.4.2. Connecting to a Network Using nmcli" /><link rel="next" href="sec-Configure_Networking-additional_resources.html" title="2.5. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li cl
ass="previous"><a accesskey="p" href="sec-Connecting_to_a_Network_Using_nmcli.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_Networking-additional_resources.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configuring_Static_Routes_Using_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.3. Configuring Static Routes Using nmcli</h3></div></div></div><div class="para">
+ To configure static routes using the <span class="application"><strong>nmcli</strong></span> tool, the interactive editor mode must be used.
+ </div><div class="example" id="ex-Configuring_Static_Routes_Using_nmcli_Editor"><h6>Example 2.3. Configuring Static Routes Using nmcli Editor</h6><div class="example-contents"><div class="para">
+ To configure a static route for an Ethernet connection using the interactive editor, issue commands as follows:
+<pre class="screen">~]$ <code class="command">nmcli con edit type ethernet con-name <em class="replaceable"><code>eth0</code></em></code>
+
+===| nmcli interactive connection editor |===
+
+Adding a new '802-3-ethernet' connection
+
+Type 'help' or '?' for available commands.
+Type 'describe [>setting<.>prop<]' for detailed property description.
+
+You may edit the following settings: connection, 802-3-ethernet (ethernet), 802-1x, ipv4, ipv6, dcb
+nmcli> set ipv4.routes 192.168.122.0/24 10.10.10.1
+nmcli>
+nmcli> save persistent
+Saving the connection with 'autoconnect=yes'. That might result in an immediate activation of the connection.
+Do you still want to save? [yes] yes
+Connection 'eth0' (704a5666-8cbd-4d89-b5f9-fa65a3dbc916) successfully saved.
+nmcli> quit
+~]$</pre>
+ </div></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Connecting_to_a_Network_Using_nmcli.html"><strong>Prev</strong>2.4.2. Connecting to a Network Using nmcli</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_Networking-additional_resources.html"><strong>Next</strong>2.5. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_Static_Routes_in_ifcfg_files.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_Static_Routes_in_ifcfg_files.html
new file mode 100644
index 0000000..ff6ac93
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_Static_Routes_in_ifcfg_files.html
@@ -0,0 +1,46 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.4. Configuring Static Routes in ifcfg files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Using_the_Command_Line_Interface.html" title="2.3. Using the Command Line Interface (CLI)" /><link rel="prev" href="sec-Static-Routes_and_the_Default_Gateway.html" title="2.3.3. Static Routes and the Default Gateway" /><link rel="next" href="sec-Configuring_IPv6_Tokenized_Interface_Identifiers.html" title="2.3.5. Configuring IPv6 Tokenized Interface Identifiers" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="
docnav"><li class="previous"><a accesskey="p" href="sec-Static-Routes_and_the_Default_Gateway.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_IPv6_Tokenized_Interface_Identifiers.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configuring_Static_Routes_in_ifcfg_files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.4. Configuring Static Routes in ifcfg files</h3></div></div></div><div class="para">
+ Static routes set using <span class="application"><strong>ip</strong></span> commands on the command line will be lost if the system is shutdown or restarted. To configure static routes to be persistent after a system restart, they must be placed in per-interface configuration files in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory. The file name should be of the format <code class="filename">route-<em class="replaceable"><code>ifname</code></em></code>. There are two types of commands to use in the configuration files; <span class="application"><strong>ip</strong></span> commands as explained in <a class="xref" href="sec-Configuring_Static_Routes_in_ifcfg_files.html#sec-networkscripts-static-routes-ip-command">Section 2.3.4.1, “Static Routes Using the IP Command Arguments Format”</a> and the <em class="firstterm">Network/Netmask</em> format as explained in <a class="xref" href="sec-Configuring_Static_Routes_in_ifcfg_files.html#sec-netwo
rkscripts-static-routes-network-netmask-directives">Section 2.3.4.2, “Network/Netmask Directives Format”</a>.
+ </div><div class="section" id="sec-networkscripts-static-routes-ip-command"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.4.1. Static Routes Using the IP Command Arguments Format</h4></div></div></div><div class="para">
+ If required in a per-interface configuration file, for example <code class="filename">/etc/sysconfig/network-scripts/route-eth0</code>, define a route to a default gateway on the first line. This is only required if the gateway is not set via <code class="systemitem">DHCP</code> and is not set globally in the <code class="filename">/etc/sysconfig/network</code> file:
+ </div><pre class="synopsis">default via <em class="replaceable"><code>192.168.1.1</code></em> <code class="option">dev</code> <em class="replaceable"><code>interface</code></em></pre><div class="para">
+ where <em class="replaceable"><code>192.168.1.1</code></em> is the <code class="systemitem">IP</code> address of the default gateway. The <em class="replaceable"><code>interface</code></em> is the interface that is connected to, or can reach, the default gateway. The <code class="option">dev</code> option can be omitted, it is optional. Note that this setting takes precedence over a setting in the <code class="filename">/etc/sysconfig/network</code> file.
+ </div><div class="para">
+ If a route to a remote network is required, a static route can be specified as follows. Each line is parsed as an individual route:
+ </div><pre class="synopsis"><em class="replaceable"><code>10.10.10.0/24</code></em> via <em class="replaceable"><code>192.168.1.1</code></em> [<span class="optional"><code class="option">dev</code> <em class="replaceable"><code>interface</code></em></span>]</pre><div class="para">
+ where <em class="replaceable"><code>10.10.10.0/24</code></em> is the network address and prefix length of the remote or destination network. The address <em class="replaceable"><code>192.168.1.1</code></em> is the <code class="systemitem">IP</code> address leading to the remote network. It is preferably the <em class="firstterm">next hop address</em> but the address of the exit interface will work. The <span class="quote">“<span class="quote">next hop</span>”</span> means the remote end of a link, for example a gateway or router. The <code class="option">dev</code> option can be used to specify the exit interface <em class="replaceable"><code>interface</code></em> but it is not required. Add as many static routes as required.
+ </div><div class="para">
+ The following is an example of a <code class="filename">route-<em class="replaceable"><code>interface</code></em></code> file using the <span class="application"><strong>ip</strong></span> command arguments format. The default gateway is <code class="systemitem">192.168.0.1</code>, interface <span class="interface">eth0</span> and a leased line or WAN connection is available at <code class="systemitem">192.168.0.10</code>. The two static routes are for reaching the <code class="systemitem">10.10.10.0/24</code> network and the <code class="systemitem">172.16.1.10/32</code> host:
+ </div><pre class="screen">default via 192.168.0.1 dev eth0
+10.10.10.0/24 via 192.168.0.10 dev eth0
+172.16.1.10/32 via 192.168.0.10 dev eth0</pre><div class="para">
+ In the above example, packets going to the local <code class="systemitem">192.168.0.0/24</code> network will be directed out the interface attached to that network. Packets going to the <code class="systemitem">10.10.10.0/24</code> network and <code class="systemitem">172.16.1.10/32</code> host will be directed to <code class="systemitem">192.168.0.10</code>. Packets to unknown, remote, networks will use the default gateway therefore static routes should only be configured for remote networks or hosts if the default route is not suitable. Remote in this context means any networks or hosts that are not directly attached to the system.
+ </div><div class="para">
+ Specifying an exit interface is optional. It can be useful if you want to force traffic out of a specific interface. For example, in the case of a VPN, you can force traffic to a remote network to pass through a <span class="interface">tun0</span> interface even when the interface is in a different subnet to the destination network.
+ </div><div class="important"><div class="admonition_header"><h2>Duplicate default gateways</h2></div><div class="admonition"><div class="para">
+ If the default gateway is already assigned by <code class="systemitem">DHCP</code> and if the same gateway with the same metric is specified in a configuration file, an error during start-up, or when bringing up an interface, will occur. The follow error message may be shown: "RTNETLINK answers: File exists". This error may be ignored.
+ </div></div></div></div><div class="section" id="sec-networkscripts-static-routes-network-netmask-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.4.2. Network/Netmask Directives Format</h4></div></div></div><div class="para">
+ You can also use the network/netmask directives format for <code class="filename">route-<em class="replaceable"><code>interface</code></em></code> files. The following is a template for the network/netmask format, with instructions following afterwards:
+ </div><pre class="synopsis"> ADDRESS0=<em class="replaceable"><code>10.10.10.0</code></em> NETMASK0=<em class="replaceable"><code>255.255.255.0</code></em> GATEWAY0=<em class="replaceable"><code>192.168.1.1</code></em> </pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>10.10.10.0</code></em></code> is the network address of the remote network or host to be reached.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">NETMASK0=<em class="replaceable"><code>255.255.255.0</code></em></code> is the netmask for the network address defined with <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>10.10.10.0</code></em></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">GATEWAY0=<em class="replaceable"><code>192.168.1.1</code></em></code> is the default gateway, or an <code class="systemitem">IP</code> address that can be used to reach <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>10.10.10.0</code></em></code>
+ </div></li></ul></div><div class="para">
+ The following is an example of a <code class="filename">route-<em class="replaceable"><code>interface</code></em></code> file using the network/netmask directives format. The default gateway is <code class="systemitem">192.168.0.1</code> but a leased line or WAN connection is available at <code class="systemitem">192.168.0.10</code>. The two static routes are for reaching the <code class="systemitem">10.10.10.0/24</code> and <code class="systemitem">172.16.1.0/24</code> networks:
+ </div><pre class="programlisting">ADDRESS0=10.10.10.0
+NETMASK0=255.255.255.0
+GATEWAY0=192.168.0.10
+ADDRESS1=172.16.1.10
+NETMASK1=255.255.255.0
+GATEWAY1=192.168.0.10</pre><div class="para">
+ Subsequent static routes must be numbered sequentially, and must not skip any values. For example, <code class="computeroutput">ADDRESS0</code>, <code class="computeroutput">ADDRESS1</code>, <code class="computeroutput">ADDRESS2</code>, and so on.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Static-Routes_and_the_Default_Gateway.html"><strong>Prev</strong>2.3.3. Static Routes and the Default Gateway</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_IPv6_Tokenized_Interface_Identifiers.html"><strong>Next</strong>2.3.5. Configuring IPv6 Tokenized Interface Ident...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_a_Multihomed_DHCP_Server.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_a_Multihomed_DHCP_Server.html
new file mode 100644
index 0000000..213ee05
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_a_Multihomed_DHCP_Server.html
@@ -0,0 +1,110 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.4. Configuring a Multihomed DHCP Server</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-DHCP_Servers.html" title="Chapter 9. DHCP Servers" /><link rel="prev" href="sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent.html" title="9.3.2. Configure dhcrelay as a DHCPv6 relay agent" /><link rel="next" href="sec-dhcp_for_ipv6_dhcpv6.html" title="9.5. DHCP for IPv6 (DHCPv6)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_dhcrelay_as_a_DHCPv6
_relay_agent.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-dhcp_for_ipv6_dhcpv6.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configuring_a_Multihomed_DHCP_Server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.4. Configuring a Multihomed DHCP Server</h2></div></div></div><a id="idm225453796800" class="indexterm"></a><div class="para">
+ A multihomed <code class="systemitem">DHCP</code> server serves multiple networks, that is, multiple subnets. The examples in these sections detail how to configure a <code class="systemitem">DHCP</code> server to serve multiple networks, select which network interfaces to listen on, and how to define network settings for systems that move networks.
+ </div><div class="para">
+ Before making any changes, back up the existing <code class="filename">/etc/dhcp/dhcpd.conf</code> file.
+ </div><div class="para">
+ The <code class="systemitem">DHCP</code> daemon will only listen on interfaces for which it finds a subnet declaration in the <code class="filename">/etc/dhcp/dhcpd.conf</code> file.
+ </div><div class="para">
+ The following is a basic <code class="filename">/etc/dhcp/dhcpd.conf</code> file, for a server that has two network interfaces, <span class="interface">eth0</span> in a <code class="systemitem">10.0.0.0/24</code> network, and <span class="interface">eth1</span> in a <code class="systemitem">172.16.0.0/24</code> network. Multiple <code class="computeroutput">subnet</code> declarations allow you to define different settings for multiple networks:
+ </div><pre class="programlisting">default-lease-time <em class="replaceable"><code>600</code></em>;
+max-lease-time <em class="replaceable"><code>7200</code></em>;
+subnet 10.0.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 10.0.0.1;
+ range 10.0.0.5 10.0.0.15;
+}
+subnet 172.16.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 172.16.0.1;
+ range 172.16.0.5 172.16.0.15;
+}</pre><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="computeroutput">subnet <em class="replaceable"><code>10.0.0.0</code></em> netmask <em class="replaceable"><code>255.255.255.0</code></em>;</code> </span></dt><dd><div class="para">
+ A <code class="computeroutput">subnet</code> declaration is required for every network your <code class="systemitem">DHCP</code> server is serving. Multiple subnets require multiple <code class="computeroutput">subnet</code> declarations. If the <code class="systemitem">DHCP</code> server does not have a network interface in a range of a <code class="computeroutput">subnet</code> declaration, the <code class="systemitem">DHCP</code> server does not serve that network.
+ </div><div class="para">
+ If there is only one <code class="computeroutput">subnet</code> declaration, and no network interfaces are in the range of that subnet, the <code class="systemitem">DHCP</code> daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="programlisting">dhcpd: No subnet declaration for eth0 (0.0.0.0).
+dhcpd: ** Ignoring requests on eth0. If this is not what
+dhcpd: you want, please write a subnet declaration
+dhcpd: in your dhcpd.conf file for the network segment
+dhcpd: to which interface eth1 is attached. **
+dhcpd:
+dhcpd:
+dhcpd: Not configured to listen on any interfaces!</pre></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">option subnet-mask <em class="replaceable"><code>255.255.255.0</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">option subnet-mask</code> option defines a subnet mask, and overrides the <code class="computeroutput">netmask</code> value in the <code class="computeroutput">subnet</code> declaration. In simple cases, the subnet and netmask values are the same.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">option routers <em class="replaceable"><code>10.0.0.1</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">option routers</code> option defines the default gateway for the subnet. This is required for systems to reach internal networks on a different subnet, as well as external networks.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">range <em class="replaceable"><code>10.0.0.5</code></em> <em class="replaceable"><code>10.0.0.15</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">range</code> option specifies the pool of available <code class="systemitem">IP</code> addresses. Systems are assigned an address from the range of specified <code class="systemitem">IP</code> addresses.
+ </div></dd></dl></div><div class="para">
+ For further information, see the <code class="filename">dhcpd.conf(5)</code> man page.
+ </div><div class="section" id="sec-dns_Host_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.4.1. Host Configuration</h3></div></div></div><a id="idm225445835984" class="indexterm"></a><div class="para">
+ Before making any changes, back up the existing <code class="filename">/etc/sysconfig/dhcpd</code> and <code class="filename">/etc/dhcp/dhcpd.conf</code> files.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm225445833136">Configuring a Single System for Multiple Networks</h5>
+ The following <code class="filename">/etc/dhcp/dhcpd.conf</code> example creates two subnets, and configures an <code class="systemitem">IP</code> address for the same system, depending on which network it connects to:
+ </div><pre class="programlisting">default-lease-time <em class="replaceable"><code>600</code></em>;
+max-lease-time <em class="replaceable"><code>7200</code></em>;
+subnet 10.0.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 10.0.0.1;
+ range 10.0.0.5 10.0.0.15;
+}
+subnet 172.16.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 172.16.0.1;
+ range 172.16.0.5 172.16.0.15;
+}
+host example0 {
+ hardware ethernet 00:1A:6B:6A:2E:0B;
+ fixed-address 10.0.0.20;
+}
+host example1 {
+ hardware ethernet 00:1A:6B:6A:2E:0B;
+ fixed-address 172.16.0.20;
+}</pre><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="computeroutput">host <em class="replaceable"><code>example0</code></em> </code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">host</code> declaration defines specific parameters for a single system, such as an <code class="systemitem">IP</code> address. To configure specific parameters for multiple hosts, use multiple <code class="computeroutput">host</code> declarations.
+ </div><div class="para">
+ Most <code class="systemitem">DHCP</code> clients ignore the name in <code class="computeroutput">host</code> declarations, and as such, this name can be anything, as long as it is unique to other <code class="computeroutput">host</code> declarations. To configure the same system for multiple networks, use a different name for each <code class="computeroutput">host</code> declaration, otherwise the <code class="systemitem">DHCP</code> daemon fails to start. Systems are identified by the <code class="computeroutput">hardware ethernet</code> option, not the name in the <code class="computeroutput">host</code> declaration.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">hardware ethernet <em class="replaceable"><code>00:1A:6B:6A:2E:0B</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">hardware ethernet</code> option identifies the system. To find this address, run the <code class="command">ip link</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">fixed-address <em class="replaceable"><code>10.0.0.20</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">fixed-address</code> option assigns a valid <code class="systemitem">IP</code> address to the system specified by the <code class="computeroutput">hardware ethernet</code> option. This address must be outside the <code class="systemitem">IP</code> address pool specified with the <code class="computeroutput">range</code> option.
+ </div></dd></dl></div><div class="para">
+ If <code class="computeroutput">option</code> statements do not end with a semicolon, the <code class="systemitem">DHCP</code> daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="programlisting">/etc/dhcp/dhcpd.conf line 20: semicolon expected.
+dhcpd: }
+dhcpd: ^
+dhcpd: /etc/dhcp/dhcpd.conf line 38: unexpected end of file
+dhcpd:
+dhcpd: ^
+dhcpd: Configuration file errors encountered -- exiting</pre><div class="formalpara"><h5 class="formalpara" id="idm225480772512">Configuring Systems with Multiple Network Interfaces</h5>
+ The following <code class="computeroutput">host</code> declarations configure a single system, which has multiple network interfaces, so that each interface receives the same <code class="systemitem">IP</code> address. This configuration will not work if both network interfaces are connected to the same network at the same time:
+ </div><pre class="programlisting">host interface0 {
+ hardware ethernet 00:1a:6b:6a:2e:0b;
+ fixed-address 10.0.0.18;
+}
+host interface1 {
+ hardware ethernet 00:1A:6B:6A:27:3A;
+ fixed-address 10.0.0.18;
+}</pre><div class="para">
+ For this example, <code class="computeroutput">interface0</code> is the first network interface, and <code class="computeroutput">interface1</code> is the second interface. The different <code class="computeroutput">hardware ethernet</code> options identify each interface.
+ </div><div class="para">
+ If such a system connects to another network, add more <code class="computeroutput">host</code> declarations, remembering to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ assign a valid <code class="computeroutput">fixed-address</code> for the network the host is connecting to.
+ </div></li><li class="listitem"><div class="para">
+ make the name in the <code class="computeroutput">host</code> declaration unique.
+ </div></li></ul></div><div class="para">
+ When a name given in a <code class="computeroutput">host</code> declaration is not unique, the <code class="systemitem">DHCP</code> daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="programlisting">dhcpd: /etc/dhcp/dhcpd.conf line 31: host interface0: already exists
+dhcpd: }
+dhcpd: ^
+dhcpd: Configuration file errors encountered -- exiting</pre><div class="para">
+ This error was caused by having multiple <code class="computeroutput">host interface0</code> declarations defined in <code class="filename">/etc/dhcp/dhcpd.conf</code>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_dhcrelay_as_a_DHCPv6_relay_agent.html"><strong>Prev</strong>9.3.2. Configure dhcrelay as a DHCPv6 relay agent</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-dhcp_for_ipv6_dhcpv6.html"><strong>Next</strong>9.5. DHCP for IPv6 (DHCPv6)</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_a_Network_Interface_Using_ip_commands.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_a_Network_Interface_Using_ip_commands.html
new file mode 100644
index 0000000..3e423f6
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_a_Network_Interface_Using_ip_commands.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.2. Configuring a Network Interface Using ip Commands</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Using_the_Command_Line_Interface.html" title="2.3. Using the Command Line Interface (CLI)" /><link rel="prev" href="sec-Using_the_Command_Line_Interface.html" title="2.3. Using the Command Line Interface (CLI)" /><link rel="next" href="sec-Static-Routes_and_the_Default_Gateway.html" title="2.3.3. Static Routes and the Default Gateway" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"
><a accesskey="p" href="sec-Using_the_Command_Line_Interface.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Static-Routes_and_the_Default_Gateway.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configuring_a_Network_Interface_Using_ip_commands"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.2. Configuring a Network Interface Using ip Commands</h3></div></div></div><div class="para">
+ The <span class="application"><strong>ip</strong></span> utility can be used to assign <code class="systemitem">IP</code> addresses to an interface. The command takes the following form: <pre class="synopsis">ip addr [<span class="optional"> add | del </span>] <em class="replaceable"><code>address</code></em> dev <em class="replaceable"><code>ifname</code></em></pre>
+ </div><h4 id="bh-Assigning_a_Static_Address_Using_ip_Commands"> Assigning a Static Address Using ip Commands </h4><div class="para">
+ To assign an <code class="systemitem">IP</code> address to an interface, issue a command as <code class="systemitem">root</code> as follows:
+<pre class="screen">~]# <code class="command">ip address add 10.0.0.3/24 dev eth0</code>
+The address assignment of a specific device can be viewed as follows:
+~]# <code class="command">ip addr show dev eth0</code>
+2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
+ link/ether f0:de:f1:7b:6e:5f brd ff:ff:ff:ff:ff:ff
+ inet 10.0.0.3/24 brd 10.0.0.255 scope global global eth0
+ valid_lft 58682sec preferred_lft 58682sec
+ inet6 fe80::f2de:f1ff:fe7b:6e5f/64 scope link
+ valid_lft forever preferred_lft forever</pre>
+ Further examples and command options can be found in the <code class="filename">ip-address(8)</code> manual page.
+ </div><h4 id="bh-Configuring_Multiple_Addresses_Using_ip_Commands"> Configuring Multiple Addresses Using ip Commands </h4><div class="para">
+ As the <span class="application"><strong>ip</strong></span> utility supports assigning multiple addresses to the same interface it is no longer necessary to use the alias interface method of binding multiple addresses to the same interface. The <span class="application"><strong>ip</strong></span> command to assign an address can be repeated multiple times in order to assign multiple address. For example:
+<pre class="screen">~]# <code class="command">ip address add 192.168.2.223/24 dev eth1</code>
+~]# <code class="command">ip address add 192.168.4.223/24 dev eth1</code>
+~]# <code class="command">ip addr</code>
+3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
+ link/ether 52:54:00:fb:77:9e brd ff:ff:ff:ff:ff:ff
+ inet 192.168.<span class="bold bold"><strong>2</strong></span>.223/24 scope global eth1
+ inet 192.168.<span class="bold bold"><strong>4</strong></span>.223/24 scope global eth1</pre>
+
+ </div><div class="para">
+ The commands for the <span class="application"><strong>ip</strong></span> utility are documented in the <code class="filename">ip(8)</code> manual page.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that <span class="application"><strong>ip</strong></span> commands given on the command line will not persist after a system restart.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_the_Command_Line_Interface.html"><strong>Prev</strong>2.3. Using the Command Line Interface (CLI)</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Static-Routes_and_the_Default_Gateway.html"><strong>Next</strong>2.3.3. Static Routes and the Default Gateway</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_a_Wi-Fi_Connection.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_a_Wi-Fi_Connection.html
new file mode 100644
index 0000000..d4ba280
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_a_Wi-Fi_Connection.html
@@ -0,0 +1,71 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.6. Configuring a Wi-Fi Connection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html" title="2.2. Using NetworkManager with the GNOME Graphical User Interface" /><link rel="prev" href="sec-Configuring_a_Wired_Ethernet_Connection.html" title="2.2.5. Configuring a Wired (Ethernet) Connection" /><link rel="next" href="sec-Establishing_a_VPN_Connection.html" title="2.2.7. Establishing a VPN Connection" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /><
/a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_a_Wired_Ethernet_Connection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_a_VPN_Connection.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configuring_a_Wi-Fi_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.6. Configuring a Wi-Fi Connection</h3></div></div></div><div class="para">
+ This section explains how to use <span class="application"><strong>NetworkManager</strong></span> to configure a Wi-Fi (also known as wireless or 802.11<em class="replaceable"><code>a/b/g/n</code></em>) connection to an Access Point.
+ </div><div class="para">
+ To configure a mobile broadband (such as 3G) connection, see <a class="xref" href="sec-Establishing_a_Mobile_Broadband_Connection.html">Section 2.2.8, “Establishing a Mobile Broadband Connection”</a>.
+ </div><h4 id="bh-Quickly_Connecting_to_an_Available_Access_Point">Quickly Connecting to an Available Access Point</h4><div class="para">
+ The easiest way to connect to an available access point is to click on the network connection icon to activate the network connection, locate the <em class="firstterm">Service Set Identifier</em> (<acronym class="acronym">SSID</acronym>) of the access point in the list of <span class="guilabel"><strong>Wi-Fi</strong></span> networks, and click on it. A padlock symbol indicates the access point requires authentication. If the access point is secured, a dialog prompts you for an authentication key or password.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> tries to auto-detect the type of security used by the access point. If there are multiple possibilities, <span class="application"><strong>NetworkManager</strong></span> guesses the security type and presents it in the <span class="guilabel"><strong>Wi-Fi security</strong></span> drop-down menu. For WPA-PSK security (WPA with a passphrase) no choice is necessary. For WPA Enterprise (802.1X) you have to specifically select the security, because that cannot be auto-detected. If you are unsure, try connecting to each type in turn. Finally, enter the key or passphrase in the <span class="guilabel"><strong>Password</strong></span> field. Certain password types, such as a 40-bit WEP or 128-bit WPA key, are invalid unless they are of a requisite length. The <span class="guilabel"><strong>Connect</strong></span> button will remain inactive until you enter a key of the length required for the selected security type.
To learn more about wireless security, see <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_Wi-Fi_Security">Section 2.2.10.2, “Configuring Wi-Fi Security”</a>.
+ </div><div class="para">
+ If <span class="application"><strong>NetworkManager</strong></span> connects to the access point successfully, the network connection icon will change into a graphical indicator of the wireless connection's signal strength.
+ </div><div class="para">
+ You can also edit the settings for one of these auto-created access point connections just as if you had added it yourself. The <span class="guilabel"><strong>Wi-Fi</strong></span> page of the <span class="guilabel"><strong>Network</strong></span> window has a <span class="guilabel"><strong>History</strong></span> button. Clicking it reveals a list of all the connections you have ever tried to connect to. See <a class="xref" href="sec-Configuring_a_Wi-Fi_Connection.html#sec-Editing_a_Connection_or_Creating_a_Completely_New_One">Section 2.2.6.2, “Editing a Connection, or Creating a Completely New One”</a>
+ </div><div class="section" id="sec-Connecting_to_a_Hidden_Wi-Fi_Network"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.6.1. Connecting to a Hidden Wi-Fi Network</h4></div></div></div><div class="para">
+ All access points have a <em class="firstterm">Service Set Identifier</em> (<acronym class="acronym">SSID</acronym>) to identify them. However, an access point may be configured not to broadcast its SSID, in which case it is <span class="emphasis"><em>hidden</em></span>, and will not show up in <span class="application"><strong>NetworkManager</strong></span>'s list of <span class="guilabel"><strong>Available</strong></span> networks. You can still connect to a wireless access point that is hiding its SSID as long as you know its SSID, authentication method, and secrets.
+ </div><div class="para">
+ To connect to a hidden wireless network, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> window appears. Select <span class="guilabel"><strong>Wi-Fi</strong></span> from the menu and then select <span class="guilabel"><strong>Connect to Hidden Network</strong></span> to cause a dialog to appear. If you have connected to the hidden network before, use the <span class="guilabel"><strong>Connection</strong></span> drop-down to select it, and click <span class="guibutton"><strong>Connect</strong></span>. If you have not, leave the <span class="guilabel"><strong>Connection</strong></span> drop-down as <span class="guimenuitem"><strong>New</strong></span>, enter the SSID of the hidden network, select its <span class="guilabel"><strong>Wi-Fi security</st
rong></span> method, enter the correct authentication secrets, and click <span class="guibutton"><strong>Connect</strong></span>.
+ </div><div class="para">
+ For more information on wireless security settings, see <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_Wi-Fi_Security">Section 2.2.10.2, “Configuring Wi-Fi Security”</a>.
+ </div></div><div class="section" id="sec-Editing_a_Connection_or_Creating_a_Completely_New_One"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.6.2. Editing a Connection, or Creating a Completely New One</h4></div></div></div><div class="para">
+ You can edit an existing connection that you have tried or succeeded in connecting to in the past by opening the <span class="guilabel"><strong>Wi-Fi</strong></span> page of the <span class="guilabel"><strong>Network</strong></span> dialog and selecting the gear wheel icon to the right of the Wi-Fi connection name. If the network is not currently in range, click <span class="guilabel"><strong>History</strong></span> to display past connections. When you click the gear wheel icon the editing connection dialog appears. The <span class="guilabel"><strong>Details</strong></span> window shows the connection details.
+ </div><div class="para">
+ To configure a new connection whose SSID is in range, first attempt to connect to it by opening the <span class="guilabel"><strong>Network</strong></span> window, selecting the <span class="guilabel"><strong>Wi-Fi</strong></span> menu entry, and clicking the connection name (by default, the same as the SSID). If the SSID is not in range, see <a class="xref" href="sec-Configuring_a_Wi-Fi_Connection.html#sec-Connecting_to_a_Hidden_Wi-Fi_Network">Section 2.2.6.1, “Connecting to a Hidden Wi-Fi Network”</a>. If the SSID is in range, the procedure is as follows:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Wi-Fi</strong></span> interface from the left-hand-side menu entry.
+ </div></li><li class="step"><div class="para">
+ Click the Wi-Fi connection profile on the right-hand side menu you want to connect to. A padlock symbol indicates a key or password is required.
+ </div></li><li class="step"><div class="para">
+ If requested, enter the authentication details.
+ </div></li></ol></div><h5 id="bh-Configuring_the_SSID-Connect_Behavior_and_Availability_Settings-wireless">Configuring the SSID, Auto-Connect Behavior, and Availability Settings</h5><div class="para">
+ To edit a Wi-Fi connection's settings, select <span class="guilabel"><strong>Wi-Fi</strong></span> in the <span class="guilabel"><strong>Network</strong></span> page and then select the gear wheel icon to the right of the Wi-Fi connection name. Select <span class="guilabel"><strong>Identity</strong></span>. The following settings are available:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>SSID</strong></span> </span></dt><dd><div class="para">
+ The <em class="firstterm">Service Set Identifier</em> (<acronym class="acronym">SSID</acronym>) of the access point (AP).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>BSSID</strong></span> </span></dt><dd><div class="para">
+ The <em class="firstterm">Basic Service Set Identifier</em> (<acronym class="acronym">BSSID</acronym>) is the MAC address, also known as a <em class="firstterm">hardware address</em>, of the specific wireless access point you are connecting to when in <span class="guilabel"><strong>Infrastructure</strong></span> mode. This field is blank by default, and you are able to connect to a wireless access point by <span class="guilabel"><strong>SSID</strong></span> without having to specify its <span class="guilabel"><strong>BSSID</strong></span>. If the BSSID is specified, it will force the system to associate to a specific access point only.
+ </div><div class="para">
+ For ad-hoc networks, the <span class="guilabel"><strong>BSSID</strong></span> is generated randomly by the <span class="application"><strong>mac80211</strong></span> subsystem when the ad-hoc network is created. It is not displayed by <span class="application"><strong>NetworkManager</strong></span>
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>MAC address</strong></span> </span></dt><dd><div class="para">
+ Select the MAC address, also known as a <em class="firstterm">hardware address</em>, of the Wi-Fi interface to use.
+ </div><div class="para">
+ A single system could have one or more wireless network adapters connected to it. The <span class="guilabel"><strong>MAC address</strong></span> field therefore allows you to associate a specific wireless adapter with a specific connection (or connections).
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Cloned Address</strong></span> </span></dt><dd><div class="para">
+ A cloned MAC address to use in place of the real hardware address. Leave blank unless required.
+ </div></dd></dl></div><div class="para">
+ The following settings are common to all connection profiles:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Make available to other users</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="sec-System-wide_and_Private_Connection_Profiles.html">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li></ul></div><h5 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-wireless">Saving Your New (or Modified) Connection and Making Further Configurations</h5><div class="para">
+ Once you have finished editing the wireless connection, click the <span class="guibutton"><strong>Apply</strong></span> button to save your configuration. Given a correct configuration, you can connect to your modified connection by selecting it from the GNOME Shell notification area menu in the top right-hand corner of the screen. Click in the top right-hand side corner to open the menu. Select <span class="guimenuitem"><strong>Wi-Fi</strong></span>. See <a class="xref" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for details on selecting and connecting to a network.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network</strong></span> window and clicking the gear wheel icon to reveal the connection details.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ security authentication for the wireless connection, click <span class="guilabel"><strong>Security</strong></span> and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_Wi-Fi_Security">Section 2.2.10.2, “Configuring Wi-Fi Security”</a>;
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click <span class="guilabel"><strong>IPv4</strong></span> and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv6</code> settings for the connection, click <span class="guilabel"><strong>IPv6</strong></span> and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv6_Settings">Section 2.2.10.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_a_Wired_Ethernet_Connection.html"><strong>Prev</strong>2.2.5. Configuring a Wired (Ethernet) Connection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_a_VPN_Connection.html"><strong>Next</strong>2.2.7. Establishing a VPN Connection</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_a_Wired_Ethernet_Connection.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_a_Wired_Ethernet_Connection.html
new file mode 100644
index 0000000..9bbb543
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Configuring_a_Wired_Ethernet_Connection.html
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.5. Configuring a Wired (Ethernet) Connection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html" title="2.2. Using NetworkManager with the GNOME Graphical User Interface" /><link rel="prev" href="sec-System-wide_and_Private_Connection_Profiles.html" title="2.2.4. System-wide and Private Connection Profiles" /><link rel="next" href="sec-Configuring_a_Wi-Fi_Connection.html" title="2.2.6. Configuring a Wi-Fi Connection" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation S
ite" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-System-wide_and_Private_Connection_Profiles.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_a_Wi-Fi_Connection.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configuring_a_Wired_Ethernet_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.5. Configuring a Wired (Ethernet) Connection</h3></div></div></div><div class="para">
+ To configure a wired network connection, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div><div class="para">
+ Select the <span class="guilabel"><strong>Wired</strong></span> network interface from the left-hand-side menu if it is not already highlighted.
+ </div><div class="para">
+ The system creates and configures a single wired <em class="firstterm">connection profile</em> called <span class="guilabel"><strong>Wired</strong></span> by default. A profile is a named collection of settings that can be applied to an interface. More than one profile can be created for an interface and applied as needed. The default profile cannot be deleted but its settings can be changed. You can edit the default <span class="guilabel"><strong>Wired</strong></span> profile by clicking the gear wheel icon. You can create a new wired connection profile by clicking the <span class="guilabel"><strong>Add Profile</strong></span> button. Connection profiles associated with a selected interface are shown on the right-hand side menu.
+ </div><div class="para">
+ When you add a new connection by clicking the <span class="guibutton"><strong>Add Profile</strong></span> button, <span class="application"><strong>NetworkManager</strong></span> creates a new configuration file for that connection and then opens the same dialog that is used for editing an existing connection. The difference between these dialogs is that an existing connection profile has a <span class="guilabel"><strong>Details</strong></span> and <span class="guilabel"><strong>Reset</strong></span> menu entry. In effect, you are always editing a connection profile; the difference only lies in whether that connection previously existed or was just created by <span class="application"><strong>NetworkManager</strong></span> when you clicked <span class="guibutton"><strong>Add Profile</strong></span>.
+ </div><div class="section" id="sec-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-wired"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.5.1. Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4></div></div></div><div class="para">
+ Many settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types, see the <span class="guilabel"><strong>Identity</strong></span> view if using the GNOME tool or the <span class="guilabel"><strong>General</strong></span> tab if using <span class="application"><strong>nm-connection-editor</strong></span>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the menu of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>MAC Address</strong></span> — Select the MAC address of the interface this profile must be applied to.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Cloned Address</strong></span> — If required, enter a different MAC address to use.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>MTU</strong></span> — If required, enter a specific <em class="firstterm">maximum transmission unit</em> (<acronym class="acronym">MTU</acronym>) to use. The MTU value represents the size in bytes of the largest packet that the link-layer will transmit. This value defaults to <code class="constant">1500</code> and does not generally need to be specified or changed.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Firewall Zone</strong></span> — If required, select a different firewall zone to apply. See the <em class="citetitle"><a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/">Red Hat Enterprise Linux 7 Security Guide</a></em> for more information on firewall zones.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect Automatically</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Make available to other users</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="sec-System-wide_and_Private_Connection_Profiles.html">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to VPN when using this connection</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the selected VPN connection when this connection profile is connected. Select the VPN from the drop-down menu.
+ </div></li></ul></div><h5 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-Wired">Saving Your New (or Modified) Connection and Making Further Configurations</h5><div class="para">
+ Once you have finished editing your wired connection, click the <span class="guibutton"><strong>Apply</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network</strong></span> window and clicking the gear wheel icon to return to the editing dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ port-based Network Access Control (PNAC), click the <span class="guilabel"><strong>802.1X Security</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_802.1X_Security">Section 2.2.10.1, “Configuring 802.1X Security”</a>;
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv6</code> settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv6_Settings">Section 2.2.10.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-System-wide_and_Private_Connection_Profiles.html"><strong>Prev</strong>2.2.4. System-wide and Private Connection Profiles</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_a_Wi-Fi_Connection.html"><strong>Next</strong>2.2.6. Configuring a Wi-Fi Connection</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Connecting_to_a_Network_Automatically.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Connecting_to_a_Network_Automatically.html
new file mode 100644
index 0000000..55c4359
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Connecting_to_a_Network_Automatically.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.3. Connecting to a Network Automatically</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html" title="2.2. Using NetworkManager with the GNOME Graphical User Interface" /><link rel="prev" href="sec-Configuring_New_and_Editing_Existing_Connections.html" title="2.2.2. Configuring New and Editing Existing Connections" /><link rel="next" href="sec-System-wide_and_Private_Connection_Profiles.html" title="2.2.4. System-wide and Private Connection Profiles" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/i
mage_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_New_and_Editing_Existing_Connections.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-System-wide_and_Private_Connection_Profiles.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Connecting_to_a_Network_Automatically"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.3. Connecting to a Network Automatically</h3></div></div></div><div class="para">
+ For any connection type you add or configure, you can choose whether you want <span class="application"><strong>NetworkManager</strong></span> to try to connect to that network automatically when it is available.
+ </div><div class="procedure" id="procedure-Configuring_NetworkManager_to_Connect_to_a_Network_Automatically_When_Detected"><h6>Procedure 2.1. Configuring NetworkManager to Connect to a Network Automatically When Detected</h6><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the network interface from the left-hand-side menu.
+ </div></li><li class="step"><div class="para">
+ Click on the gear wheel icon of a connection profile on the right-hand side menu. If you have only one profile associated with the selected interface the gear wheel icon will be in the lower right-hand-side corner. The <span class="guilabel"><strong>Network</strong></span> details window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Identity</strong></span> menu entry on the left. The <span class="guilabel"><strong>Network</strong></span> window changes to the identity view.
+ </div></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Connect automatically</strong></span> to cause <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the connection whenever <span class="application"><strong>NetworkManager</strong></span> detects that it is available. Clear the check box if you do not want <span class="application"><strong>NetworkManager</strong></span> to connect automatically. If the check box is clear, you will have to select that connection manually in the network settings tool to cause it to connect.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_New_and_Editing_Existing_Connections.html"><strong>Prev</strong>2.2.2. Configuring New and Editing Existing Conne...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-System-wide_and_Private_Connection_Profiles.html"><strong>Next</strong>2.2.4. System-wide and Private Connection Profiles</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Connecting_to_a_Network_Using_nmcli.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Connecting_to_a_Network_Using_nmcli.html
new file mode 100644
index 0000000..994814a
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Connecting_to_a_Network_Using_nmcli.html
@@ -0,0 +1,197 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.2. Connecting to a Network Using nmcli</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html" title="2.4. Using the NetworkManager Command Line Tool, nmcli" /><link rel="prev" href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html" title="2.4. Using the NetworkManager Command Line Tool, nmcli" /><link rel="next" href="sec-Configuring_Static_Routes_Using_nmcli.html" title="2.4.3. Configuring Static Routes Using nmcli" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation S
ite" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Static_Routes_Using_nmcli.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Connecting_to_a_Network_Using_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.2. Connecting to a Network Using nmcli</h3></div></div></div><div class="para">
+ To list the currently available network connections, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con show</code>
+NAME UUID TYPE DEVICE
+eth0 96a5deb0-5eb0-41e1-a7ed-38fea413f9c8 802-3-ethernet eth0
+MyWiFi 91451385-4eb8-4080-8b82 802-11-wireless wlan0</pre>
+ Note that the NAME field in the output always denotes the connection ID (name). It is not the interface name even though it might look the same. In the example above <code class="literal">eth0</code> is the connection ID given by the user to the profile applied to the interface <span class="interface">eth0</span>. In the second line the user has assigned the connection ID <code class="literal">MyWiFi</code> to the interface <code class="literal">wlan0</code>.
+ </div><div class="para">
+ Adding an Ethernet connection means creating a configuration profile which is then assigned to a device. Before creating a new profile, review the available devices as follows:
+<pre class="screen">~]$ <code class="command">nmcli dev status</code>
+DEVICE TYPE STATE CONNECTION
+wlan0 wifi connected my-ssid
+eth0 ethernet unavailable --
+lo loopback unmanaged --</pre>
+
+ </div><h4 id="Adding_a_Dynamic_Ethernet_Connection">Adding a Dynamic Ethernet Connection</h4><div class="para">
+ To add an Ethernet configuration profile with dynamic <code class="systemitem">IP</code> configuration, allowing <code class="systemitem">DHCP</code> to assign the network configuration, a command in the following format can be used: <pre class="synopsis">nmcli connection add type ethernet con-name <em class="replaceable"><code>connection-name</code></em> ifname <em class="replaceable"><code>interface-name</code></em></pre>
+ </div><div class="para">
+ For example, to create a dynamic connection profile named <em class="replaceable"><code>my-office</code></em>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type ethernet con-name <em class="replaceable"><code>my-office</code></em> ifname <em class="replaceable"><code>eth0</code></em></code>
+Connection 'my-office' (0a053110-5361-412c-a4fb-6ff20877e9e4) successfully added.</pre>
+ <span class="application"><strong>NetworkManager</strong></span> will set its internal parameter <code class="option">connection.autoconnect</code> to <code class="literal">yes</code>. <span class="application"><strong>NetworkManager</strong></span> will also write out settings to <code class="filename">/etc/sysconfig/network-scripts/ifcfg-my-office</code> where the ONBOOT directive will be set to <code class="literal">yes</code>.
+ </div><div class="para">
+ Note that manual changes to the ifcfg file will not be noticed by <span class="application"><strong>NetworkManager</strong></span> until the interface is next brought up. See <a class="xref" href="sec-Network_Configuration_Using_sysconfig_Files.html">Section 1.7, “Network Configuration Using sysconfig Files”</a> for more information on using configuration files.
+ </div><div class="para">
+ To bring up the Ethernet connection, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con up <em class="replaceable"><code>my-office</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/1)</pre>
+ Review the status of the devices and connections:
+<pre class="screen">~]$ <code class="command">nmcli device status</code>
+DEVICE TYPE STATE CONNECTION
+eth0 ethernet connected my-office
+lo loopback unmanaged --</pre>
+
+ </div><div class="para">
+ To change the host name sent by a host to a <code class="systemitem">DHCP</code> server, modify the <code class="option">dhcp-hostname</code> property as follows:
+<pre class="screen">~]$ <code class="command">nmcli con modify my-office <em class="replaceable"><code>my-office</code></em> ipv4.dhcp-hostname <em class="replaceable"><code>host-name</code></em> ipv6.dhcp-hostname <em class="replaceable"><code>host-name</code></em></code></pre>
+ </div><div class="para">
+ To change the <code class="systemitem">IPv4</code> client ID sent by a host to a <code class="systemitem">DHCP</code> server, modify the <code class="option">dhcp-client-id</code> property as follows:
+<pre class="screen">~]$ <code class="command">nmcli con modify my-office <em class="replaceable"><code>my-office</code></em> ipv4.dhcp-client-id <em class="replaceable"><code>client-ID-string</code></em></code></pre>
+ There is no <code class="option">dhcp-client-id</code> property for <code class="systemitem">IPv6</code>, <span class="application"><strong>dhclient</strong></span> creates an identifier for <code class="systemitem">IPv6</code>. See the <code class="filename">dhclient(8)</code> man page for details.
+ </div><div class="para">
+ To ignore the <code class="systemitem">DNS</code> servers sent to a host by a <code class="systemitem">DHCP</code> server, modify the <code class="option">ignore-auto-dns</code> property as follows:
+<pre class="screen">~]$ <code class="command">nmcli con modify my-office <em class="replaceable"><code>my-office</code></em> ipv4.ignore-auto-dns <em class="replaceable"><code>yes</code></em> ipv6.ignore-auto-dns <em class="replaceable"><code>yes</code></em></code></pre>
+ </div><div class="para">
+ See the <code class="filename">nm-settings(5)</code> man page for more information on properties and their settings.
+ </div><div class="example" id="ex-Configuring_a_Dynamic_Ethernet_Connection_Using_the_Interactive_Editor"><h6>Example 2.1. Configuring a Dynamic Ethernet Connection Using the Interactive Editor</h6><div class="example-contents"><div class="para">
+ To configure a dynamic Ethernet connection using the interactive editor, issue commands as follows:
+<pre class="screen">~]$ <code class="command">nmcli con edit type ethernet con-name <em class="replaceable"><code>eth0</code></em></code>
+
+===| nmcli interactive connection editor |===
+
+Adding a new '802-3-ethernet' connection
+
+Type 'help' or '?' for available commands.
+Type 'describe [<setting>.<prop>]' for detailed property description.
+
+You may edit the following settings: connection, 802-3-ethernet (ethernet), 802-1x, ipv4, ipv6, dcb
+nmcli> describe ipv4.method
+
+=== [method] ===
+[NM property description]
+IPv4 configuration method. If 'auto' is specified then the appropriate automatic method (DHCP, PPP, etc) is used for the interface and most other properties can be left unset. If 'link-local' is specified, then a link-local address in the 169.254/16 range will be assigned to the interface. If 'manual' is specified, static IP addressing is used and at least one IP address must be given in the 'addresses' property. If 'shared' is specified (indicating that this connection will provide network access to other computers) then the interface is assigned an address in the 10.42.x.1/24 range and a DHCP and forwarding DNS server are started, and the interface is NAT-ed to the current default network connection. 'disabled' means IPv4 will not be used on this connection. This property must be set.
+
+nmcli> set ipv4.method auto
+nmcli> save
+Saving the connection with 'autoconnect=yes'. That might result in an immediate activation of the connection.
+Do you still want to save? [yes] yes
+Connection 'eth0' (090b61f7-540f-4dd6-bf1f-a905831fc287) successfully saved.
+nmcli> quit
+~]$</pre>
+ The default action is to save the connection profile as persistent. If required, the profile can be held in memory only, until the next restart, by means of the <code class="command">save temporary</code> command.
+ </div></div></div><br class="example-break" /><h4 id="Adding_a_Static_Ethernet_Connection">Adding a Static Ethernet Connection</h4><div class="para">
+ To add an Ethernet connection with static <code class="systemitem">IPv4</code> configuration, a command in the following format can be used: <pre class="synopsis">nmcli connection add type ethernet con-name <em class="replaceable"><code>connection-name</code></em> ifname <em class="replaceable"><code>interface-name</code></em> ip4 <em class="replaceable"><code>address</code></em> gw4 <em class="replaceable"><code>address</code></em></pre> <code class="systemitem">IPv6</code> address and gateway information can be added using the <code class="option">ip6</code> and <code class="option">gw6</code> options.
+ </div><div class="para">
+ For example, a command to create a static Ethernet connection with only <code class="systemitem">IPv4</code> address and gateway is as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type ethernet con-name <em class="replaceable"><code>test-lab</code></em> ifname <em class="replaceable"><code>eth1</code></em> ip4 10.10.10.10/24 \</code>
+<code class="command">gw4 10.10.10.254</code></pre>
+ Optionally, at the same time specify <code class="systemitem">IPv6</code> address and gateway for the device as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type ethernet con-name <em class="replaceable"><code>test-lab</code></em> ifname <em class="replaceable"><code>eth1</code></em> ip4 10.10.10.10/24 \</code>
+<code class="command">gw4 10.10.10.254 ip6 abbe::cafe gw6 2001:db8::1</code>
+Connection 'test-lab' (05abfd5e-324e-4461-844e-8501ba704773) successfully added.</pre>
+ <span class="application"><strong>NetworkManager</strong></span> will set its internal parameter <code class="option">ipv4.method</code> to <code class="literal">manual</code> and <code class="option">connection.autoconnect</code> to <code class="literal">yes</code>. <span class="application"><strong>NetworkManager</strong></span> will also write out settings to <code class="filename">/etc/sysconfig/network-scripts/ifcfg-my-office</code> where the corresponding BOOTPROTO will be set to <code class="literal">none</code> and ONBOOT will be set to <code class="literal">yes</code>.
+ </div><div class="para">
+ Note that manual changes to the ifcfg file will not be noticed by <span class="application"><strong>NetworkManger</strong></span> until the interface is next brought up. See <a class="xref" href="sec-Network_Configuration_Using_sysconfig_Files.html">Section 1.7, “Network Configuration Using sysconfig Files”</a> for more information on using configuration files.
+ </div><div class="para">
+ To set two <code class="systemitem">IPv4</code> <code class="systemitem">DNS</code> server addresses:
+<pre class="screen">~]$ <code class="command">nmcli con mod <em class="replaceable"><code>test-lab</code></em> ipv4.dns "8.8.8.8 8.8.4.4"</code></pre>
+ Note that this will replace any previously set <code class="systemitem">DNS</code> servers. To set two <code class="systemitem">IPv6</code> <code class="systemitem">DNS</code> server addresses:
+<pre class="screen">~]$ <code class="command">nmcli con mod <em class="replaceable"><code>test-lab</code></em> ipv6.dns "2001:4860:4860::8888 2001:4860:4860::8844"</code></pre>
+ Note that this will replace any previously set <code class="systemitem">DNS</code> servers. Alternatively, to add additional <code class="systemitem">DNS</code> servers to any previously set, use the <code class="literal">+</code> prefix as follows:
+<pre class="screen">~]$ <code class="command">nmcli con mod <em class="replaceable"><code>test-lab</code></em> +ipv4.dns "8.8.8.8 8.8.4.4"</code></pre>
+
+<pre class="screen">~]$ <code class="command">nmcli con mod <em class="replaceable"><code>test-lab</code></em> +ipv6.dns "2001:4860:4860::8888 2001:4860:4860::8844"</code></pre>
+ </div><div class="para">
+ To bring up the new Ethernet connection, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con up <em class="replaceable"><code>test-lab</code></em> ifname <em class="replaceable"><code>eth1</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/2</pre>
+ Review the status of the devices and connections:
+<pre class="screen">~]$ <code class="command">nmcli device status</code>
+DEVICE TYPE STATE CONNECTION
+eth0 ethernet connected my-office
+eth1 ethernet connected test-lab
+lo loopback unmanaged --</pre>
+ </div><div class="para">
+ To view detailed information about the newly configured connection, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli -p con show <em class="replaceable"><code>test-lab</code></em></code>
+===============================================================================
+ Connection profile details (test-lab)
+===============================================================================
+connection.id: test-lab
+connection.uuid: 05abfd5e-324e-4461-844e-8501ba704773
+connection.interface-name: eth1
+connection.type: 802-3-ethernet
+connection.autoconnect: yes
+connection.timestamp: 1410428968
+connection.read-only: no
+connection.permissions:
+connection.zone: --
+connection.master: --
+connection.slave-type: --
+connection.secondaries:
+connection.gateway-ping-timeout: 0
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em></pre>
+ The use of the <code class="option">-p, --pretty</code> option adds a title banner and section breaks to the output.
+ </div><div class="example" id="ex-Configuring_a_Static_Ethernet_Connection_Using_the_Interactive_Editor"><h6>Example 2.2. Configuring a Static Ethernet Connection Using the Interactive Editor</h6><div class="example-contents"><div class="para">
+ To configure a static Ethernet connection using the interactive editor, issue commands as follows:
+<pre class="screen">~]$ <code class="command">nmcli con edit type ethernet con-name <em class="replaceable"><code>eth0</code></em></code>
+
+===| nmcli interactive connection editor |===
+
+Adding a new '802-3-ethernet' connection
+
+Type 'help' or '?' for available commands.
+Type 'describe [>setting<.>prop<]' for detailed property description.
+
+You may edit the following settings: connection, 802-3-ethernet (ethernet), 802-1x, ipv4, ipv6, dcb
+nmcli> set ipv4.addresses 192.168.122.88/24
+Do you also want to set 'ipv4.method' to 'manual'? [yes]: yes
+nmcli>
+nmcli> save temporary
+Saving the connection with 'autoconnect=yes'. That might result in an immediate activation of the connection.
+Do you still want to save? [yes] no
+nmcli> save
+Saving the connection with 'autoconnect=yes'. That might result in an immediate activation of the connection.
+Do you still want to save? [yes] yes
+Connection 'eth0' (704a5666-8cbd-4d89-b5f9-fa65a3dbc916) successfully saved.
+nmcli> quit
+~]$</pre>
+ The default action is to save the connection profile as persistent. If required, the profile can be held in memory only, until the next restart, by means of the <code class="command">save temporary</code> command.
+ </div></div></div><br class="example-break" /><h4 id="Locking_a_Profile_to_a_Specific_Device">Locking a Profile to a Specific Device</h4><div class="para">
+ To lock a profile to a specific interface device, the commands used in the examples above include the interface name. For example: <pre class="synopsis">nmcli connection add type ethernet con-name <em class="replaceable"><code>connection-name</code></em> ifname <em class="replaceable"><code>interface-name</code></em></pre> To make a profile usable for all compatible Ethernet interfaces, issue a command as follows: <pre class="synopsis">nmcli connection add type ethernet con-name <em class="replaceable"><code>connection-name</code></em> ifname "*"</pre> Note that you have to use the <code class="option">ifname</code> argument even if you do not want to set a specific interface. Use the wildcard character <code class="literal">*</code> to specify that the profile can be used with any compatible device.
+ </div><div class="para">
+ To lock a profile to a specific MAC address, use a command in the following format: <pre class="synopsis">nmcli connection add type ethernet con-name "<em class="replaceable"><code>connection-name</code></em>" ifname "*" mac 00:00:5E:00:53:00</pre>
+ </div><h4 id="Adding_a_Wi-Fi_Connection">Adding a Wi-Fi Connection</h4><div class="para">
+ To view the available Wi-Fi access points, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli dev wifi list</code>
+ SSID MODE CHAN RATE SIGNAL BARS SECURITY
+ FedoraTest Infra 11 54 MB/s 98 ▂▄▆█ WPA1
+ Red Hat Guest Infra 6 54 MB/s 97 ▂▄▆█ WPA2
+ Red Hat Infra 6 54 MB/s 77 ▂▄▆_ WPA2 802.1X
+* Red Hat Infra 40 54 MB/s 66 ▂▄▆_ WPA2 802.1X
+ VoIP Infra 1 54 MB/s 32 ▂▄__ WEP
+ MyCafe Infra 11 54 MB/s 39 ▂▄__ WPA2</pre>
+ </div><div class="para">
+ To create a Wi-Fi connection profile with static <code class="systemitem">IP</code> configuration, but allowing automatic <code class="systemitem">DNS</code> address assignment, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add con-name <em class="replaceable"><code>MyCafe</code></em> ifname wlan0 type wifi ssid MyCafe \</code>
+<code class="command">ip4 192.168.100.101/24 gw4 192.168.100.1</code></pre>
+ To set a WPA2 password, for example <span class="quote">“<span class="quote">caffeine</span>”</span>, issue commands as follows:
+<pre class="screen">~]$ <code class="command">nmcli con modify <em class="replaceable"><code>MyCafe</code></em> wifi-sec.key-mgmt wpa-psk</code>
+~]$ <code class="command">nmcli con modify <em class="replaceable"><code>MyCafe</code></em> wifi-sec.psk caffeine</code></pre>
+
+ </div><div class="para">
+ To change Wi-Fi state, issue a command in the following format:
+<pre class="screen">~]$ <code class="command">nmcli radio wifi [<span class="optional">on | off </span>]</code></pre>
+
+ </div><h4 id="Changing_a_Specific_Property">Changing a Specific Property</h4><div class="para">
+ To check a specific property, for example <code class="literal">mtu</code>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection show id '<em class="replaceable"><code>MyCafe</code></em>' | grep mtu</code>
+802-11-wireless.mtu: auto</pre>
+ To change the property of a setting, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection modify id '<em class="replaceable"><code>MyCafe</code></em>' 802-11-wireless.mtu 1350</code></pre>
+ To verify the change, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli connection show id '<em class="replaceable"><code>MyCafe</code></em>' | grep mtu</code>
+802-11-wireless.mtu: 1350</pre>
+
+ </div><div class="para">
+ Note that <span class="application"><strong>NetworkManager</strong></span> refers to parameters such as <code class="literal">802-3-ethernet</code> and <code class="literal">802-11-wireless</code> as the setting, and <code class="literal">mtu</code> as a property of the setting. See the <code class="filename">nm-settings(5)</code> man page for more information on properties and their settings.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html"><strong>Prev</strong>2.4. Using the NetworkManager Command Line Tool, ...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Static_Routes_Using_nmcli.html"><strong>Next</strong>2.4.3. Configuring Static Routes Using nmcli</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Consistent_Network_Device_Naming-Enabling_and_Disabling.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Consistent_Network_Device_Naming-Enabling_and_Disabling.html
new file mode 100644
index 0000000..869b67d
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Consistent_Network_Device_Naming-Enabling_and_Disabling.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.6.2. Enabling and Disabling the Feature</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Consistent_Network_Device_Naming_Using_biosdevname.html" title="8.6. Consistent Network Device Naming Using biosdevname" /><link rel="prev" href="sec-Consistent_Network_Device_Naming_Using_biosdevname.html" title="8.6. Consistent Network Device Naming Using biosdevname" /><link rel="next" href="sec-Consistent_Network_Device_Naming-Notes.html" title="8.7. Notes for Administrators" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /><
/a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Consistent_Network_Device_Naming_Using_biosdevname.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Consistent_Network_Device_Naming-Notes.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Consistent_Network_Device_Naming-Enabling_and_Disabling"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.6.2. Enabling and Disabling the Feature</h3></div></div></div><div class="para">
+ To disable this feature, pass the following option on the boot command line, both during and after installation:
+ </div><pre class="screen"><code class="option">biosdevname=0</code></pre><div class="para">
+ To enable this feature, pass the following option on the boot command line, both during and after installation:
+ </div><pre class="screen"><code class="option">biosdevname=1</code></pre><div class="para">
+ Unless the system meets the minimum requirements, this option will be ignored and the system will use the <code class="systemitem">systemd</code> naming scheme as described in the beginning of the chapter.
+ </div><div class="para">
+ If the <code class="option">biosdevname</code> install option is specified, it must remain as a boot option for the lifetime of the system.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Consistent_Network_Device_Naming_Using_biosdevname.html"><strong>Prev</strong>8.6. Consistent Network Device Naming Using biosd...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Consistent_Network_Device_Naming-Notes.html"><strong>Next</strong>8.7. Notes for Administrators</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Consistent_Network_Device_Naming-Notes.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Consistent_Network_Device_Naming-Notes.html
new file mode 100644
index 0000000..fc63754
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Consistent_Network_Device_Naming-Notes.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.7. Notes for Administrators</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Consistent_Network_Device_Naming.html" title="Chapter 8. Consistent Network Device Naming" /><link rel="prev" href="sec-Consistent_Network_Device_Naming-Enabling_and_Disabling.html" title="8.6.2. Enabling and Disabling the Feature" /><link rel="next" href="sec-Controlling_the_Selection_of_Network_Device_Names.html" title="8.8. Controlling the Selection of Network Device Names" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a>
</p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Consistent_Network_Device_Naming-Enabling_and_Disabling.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Controlling_the_Selection_of_Network_Device_Names.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Consistent_Network_Device_Naming-Notes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.7. Notes for Administrators</h2></div></div></div><div class="para">
+ Many system customization files can include network interface names, and thus will require updates if moving a system from the old convention to the new convention. If you use the new naming convention, you will also need to update network interface names in areas such as custom <span class="application"><strong>iptables</strong></span> rules, scripts altering <code class="systemitem">irqbalance</code>, and other similar configuration files. Also, enabling this change for installation will require modification to existing <span class="application"><strong>kickstart</strong></span> files that use device names via the <code class="option">ksdevice</code> parameter; these <span class="application"><strong>kickstart</strong></span> files will need to be updated to use the network device's MAC address or the network device's new name.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The maximum interface name length is defined by the kernel headers and is a global limit, affecting all applications.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Consistent_Network_Device_Naming-Enabling_and_Disabling.html"><strong>Prev</strong>8.6.2. Enabling and Disabling the Feature</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Controlling_the_Selection_of_Network_Device_Names.html"><strong>Next</strong>8.8. Controlling the Selection of Network Device ...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Consistent_Network_Device_Naming-additional_resources.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Consistent_Network_Device_Naming-additional_resources.html
new file mode 100644
index 0000000..b66cdf5
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Consistent_Network_Device_Naming-additional_resources.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.11. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Consistent_Network_Device_Naming.html" title="Chapter 8. Consistent Network Device Naming" /><link rel="prev" href="sec_Troubleshooting_Network_Device_Naming.html" title="8.10. Troubleshooting Network Device Naming" /><link rel="next" href="part-Servers.html" title="Part II. Servers" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec_Troubleshooting_Network
_Device_Naming.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="part-Servers.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Consistent_Network_Device_Naming-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.11. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding Network Teaming.
+ </div><div class="section" id="sec-Consistent_Network_Device_Naming-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.11.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">udev(7)</code> man page — Describes the Linux dynamic device management daemon, <code class="systemitem">udevd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">systemd(1)</code> man page — Describes <code class="systemitem">systemd</code> system and service manager.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">biosdevname(1)</code> man page — Describes the utility for obtaining the BIOS-given name of a device.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec_Troubleshooting_Network_Device_Naming.html"><strong>Prev</strong>8.10. Troubleshooting Network Device Naming</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="part-Servers.html"><strong>Next</strong>Part II. Servers</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Consistent_Network_Device_Naming_Using_biosdevname.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Consistent_Network_Device_Naming_Using_biosdevname.html
new file mode 100644
index 0000000..37c1911
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Consistent_Network_Device_Naming_Using_biosdevname.html
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.6. Consistent Network Device Naming Using biosdevname</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Consistent_Network_Device_Naming.html" title="Chapter 8. Consistent Network Device Naming" /><link rel="prev" href="sec-Naming_Scheme_for_VLAN_Interfaces.html" title="8.5. Naming Scheme for VLAN Interfaces" /><link rel="next" href="sec-Consistent_Network_Device_Naming-Enabling_and_Disabling.html" title="8.6.2. Enabling and Disabling the Feature" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class
="previous"><a accesskey="p" href="sec-Naming_Scheme_for_VLAN_Interfaces.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Consistent_Network_Device_Naming-Enabling_and_Disabling.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Consistent_Network_Device_Naming_Using_biosdevname"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.6. Consistent Network Device Naming Using biosdevname</h2></div></div></div><div class="para">
+ This feature, implemented via the <span class="application"><strong>biosdevname</strong></span> <span class="application"><strong>udev</strong></span> helper utility, will change the name of all embedded network interfaces, PCI card network interfaces, and virtual function network interfaces from the existing <code class="interfacename">eth[0123…]</code> to the new naming convention as shown in <a class="xref" href="sec-Consistent_Network_Device_Naming_Using_biosdevname.html#tabl-Consistent_Network_Device_Naming_biosdevname">Table 8.3, “The biosdevname Naming Convention”</a>. Note that unless the system is a Dell system, or <span class="application"><strong>biosdevname</strong></span> is explicitly enabled as described in <a class="xref" href="sec-Consistent_Network_Device_Naming-Enabling_and_Disabling.html">Section 8.6.2, “Enabling and Disabling the Feature”</a>, the <code class="systemitem">systemd</code> naming scheme will take precedence.
+ </div><div class="table" id="tabl-Consistent_Network_Device_Naming_biosdevname"><h6>Table 8.3. The biosdevname Naming Convention</h6><div class="table-contents"><table summary="The biosdevname Naming Convention" border="1"><colgroup><col width="35%" class="device" /><col width="15%" class="old" /><col width="50%" class="new" /></colgroup><thead><tr><th class="">
+ Device
+ </th><th class="">
+ Old Name
+ </th><th class="">
+ New Name
+ </th></tr></thead><tbody><tr><td class="">
+ Embedded network interface (LOM)
+ </td><td class="">
+ <code class="interfacename">eth[0123…]</code>
+ </td><td class="">
+ <code class="interfacename">em[1234…]</code><a href="#ftn.idm225482265296" class="footnote"><sup class="footnote" id="idm225482265296">[a]</sup></a>
+ </td></tr><tr><td class="">
+ PCI card network interface
+ </td><td class="">
+ <code class="interfacename">eth[0123…]</code>
+ </td><td class="">
+ <code class="interfacename">p<<em class="replaceable"><code>slot</code></em>>p<<em class="replaceable"><code>ethernet port</code></em>></code><a href="#ftn.idm225453515680" class="footnote"><sup class="footnote" id="idm225453515680">[b]</sup></a>
+ </td></tr><tr><td class="">
+ Virtual function
+ </td><td class="">
+ <code class="interfacename">eth[0123…]</code>
+ </td><td class="">
+ <code class="interfacename">p<<em class="replaceable"><code>slot</code></em>>p<<em class="replaceable"><code>ethernet port</code></em>>_<<em class="replaceable"><code>virtual interface</code></em>></code><a href="#ftn.idm225453510112" class="footnote"><sup class="footnote" id="idm225453510112">[c]</sup></a>
+ </td></tr></tbody><tbody class="footnotes"><tr><td colspan="3"><div id="ftn.idm225482265296" class="footnote"><div class="para"><a href="#idm225482265296" class="para"><sup class="para">[a] </sup></a>
+ New enumeration starts at <code class="literal">1</code>.
+ </div></div><div id="ftn.idm225453515680" class="footnote"><div class="para"><a href="#idm225453515680" class="para"><sup class="para">[b] </sup></a>
+ For example: <code class="interfacename">p3p4</code>
+ </div></div><div id="ftn.idm225453510112" class="footnote"><div class="para"><a href="#idm225453510112" class="para"><sup class="para">[c] </sup></a>
+ For example: <code class="interfacename">p3p4_1</code>
+ </div></div></td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="sec-Consistent_Network_Device_Naming-System_Requirements"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.6.1. System Requirements</h3></div></div></div><div class="para">
+ The <span class="application"><strong>biosdevname</strong></span> program uses information from the system's BIOS, specifically the <span class="emphasis"><em>type 9</em></span> (System Slot) and <span class="emphasis"><em>type 41</em></span> (Onboard Devices Extended Information) fields contained within the SMBIOS. If the system's BIOS does not have SMBIOS version 2.6 or higher and this data, the new naming convention will not be used. Most older hardware does not support this feature because of a lack of BIOSes with the correct SMBIOS version and field information. For BIOS or SMBIOS version information, contact your hardware vendor.
+ </div><div class="para">
+ For this feature to take effect, the <span class="package">biosdevname</span> package must also be installed. To install it, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">yum install biosdevname</code></pre>
+
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Naming_Scheme_for_VLAN_Interfaces.html"><strong>Prev</strong>8.5. Naming Scheme for VLAN Interfaces</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Consistent_Network_Device_Naming-Enabling_and_Disabling.html"><strong>Next</strong>8.6.2. Enabling and Disabling the Feature</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Controlling_teamd_with_teamdctl.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Controlling_teamd_with_teamdctl.html
new file mode 100644
index 0000000..3ed5264
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Controlling_teamd_with_teamdctl.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.11. Controlling teamd with teamdctl</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Teaming.html" title="Chapter 5. Configure Network Teaming" /><link rel="prev" href="sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl.html" title="5.10.9. Setting the Active Port Options of a Team Using teamnl" /><link rel="next" href="sec-Remove_a_Port_From_a_Network_Team.html" title="5.11.2. Remove a Port From a Network Team" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li cla
ss="previous"><a accesskey="p" href="sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Remove_a_Port_From_a_Network_Team.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Controlling_teamd_with_teamdctl"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.11. Controlling teamd with teamdctl</h2></div></div></div><div class="para">
+ In order to query a running instance of <code class="systemitem">teamd</code> for statistics or configuration information, or to make changes, the control tool <span class="application"><strong>teamdctl</strong></span> is used.
+ </div><div class="para">
+ To view the current team state of a team <span class="interface">team0</span>, enter the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamdctl team0 state view</code></pre>
+ For a more verbose output:
+<pre class="screen">~]# <code class="command">teamdctl team0 state view -v</code></pre>
+ </div><div class="para">
+ For a complete state dump in JSON format (useful for machine processing) of <span class="interface">team0</span>, use the following command:
+<pre class="screen">~]# <code class="command">teamdctl team0 state dump</code></pre>
+ </div><div class="para">
+ For a configuration dump in JSON format of <span class="interface">team0</span>, use the following command:
+<pre class="screen">~]# <code class="command">teamdctl team0 config dump</code></pre>
+ </div><div class="para">
+ To view the configuration of a port <span class="interface">em1</span>, that is part of a team <span class="interface">team0</span>, enter the following command:
+<pre class="screen">~]# <code class="command">teamdctl team0 port config dump em1</code></pre>
+ </div><div class="section" id="sec-Add_a_port_to_a_Network_Team"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.11.1. Add a Port to a Network Team</h3></div></div></div><div class="para">
+ To add a port <span class="interface">em1</span> to a network team <span class="interface">team0</span>, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamdctl team0 port add em1</code></pre>
+
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl.html"><strong>Prev</strong>5.10.9. Setting the Active Port Options of a Team...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Remove_a_Port_From_a_Network_Team.html"><strong>Next</strong>5.11.2. Remove a Port From a Network Team</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Controlling_the_Selection_of_Network_Device_Names.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Controlling_the_Selection_of_Network_Device_Names.html
new file mode 100644
index 0000000..8edfc33
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Controlling_the_Selection_of_Network_Device_Names.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.8. Controlling the Selection of Network Device Names</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Consistent_Network_Device_Naming.html" title="Chapter 8. Consistent Network Device Naming" /><link rel="prev" href="sec-Consistent_Network_Device_Naming-Notes.html" title="8.7. Notes for Administrators" /><link rel="next" href="sec-Disabling_Consistent_Network_Device_Naming.html" title="8.9. Disabling Consistent Network Device Naming" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"
><a accesskey="p" href="sec-Consistent_Network_Device_Naming-Notes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Disabling_Consistent_Network_Device_Naming.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Controlling_the_Selection_of_Network_Device_Names"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.8. Controlling the Selection of Network Device Names</h2></div></div></div><div class="para">
+ Device naming can be controlled in the following manner:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">By identifying the network interface device</span></dt><dd><div class="para">
+ Setting the MAC address in an <code class="filename">ifcfg</code> file using the <code class="command">HWADDR</code> directive enables it to be identified by <span class="application"><strong>udev</strong></span>. The name will be taken from the string given by the <code class="command">DEVICE</code> directive, which by convention is the same as the <code class="filename">ifcfg</code> suffix. For example, <code class="filename">ifcfg</code>-<em class="replaceable"><code>eth0</code></em>.
+ </div></dd><dt class="varlistentry"><span class="term">By turning on or off <span class="application"><strong>biosdevname</strong></span></span></dt><dd><div class="para">
+ The name provided by <span class="application"><strong>biosdevname</strong></span> will be used (if <span class="application"><strong>biosdevname</strong></span> can determine one).
+ </div></dd><dt class="varlistentry"><span class="term">By turning on or off the <code class="systemitem">systemd-udev</code> naming scheme</span></dt><dd><div class="para">
+ The name provided by <code class="systemitem">systemd-udev</code> will be used (if <code class="systemitem">systemd-udev</code> can determine one).
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Consistent_Network_Device_Naming-Notes.html"><strong>Prev</strong>8.7. Notes for Administrators</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Disabling_Consistent_Network_Device_Naming.html"><strong>Next</strong>8.9. Disabling Consistent Network Device Naming</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Converting_a_Bond_to_a_Team.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Converting_a_Bond_to_a_Team.html
new file mode 100644
index 0000000..3572e6c
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Converting_a_Bond_to_a_Team.html
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.6. Converting a Bond to a Team</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Teaming.html" title="Chapter 5. Configure Network Teaming" /><link rel="prev" href="sec-Install_the_Network_Teaming_Daemon.html" title="5.5. Install the Network Teaming Daemon" /><link rel="next" href="sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team.html" title="5.7. Selecting Interfaces to Use as Ports for a Network Team" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec-Install_the_Network_Teaming_Daemon.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Converting_a_Bond_to_a_Team"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.6. Converting a Bond to a Team</h2></div></div></div><div class="para">
+ It is possible to convert existing bonding configuration files to team configuration files using the <span class="application"><strong>bond2team</strong></span> tool. It can convert bond configuration files in <code class="filename">ifcfg</code> format to team configuration files in either <code class="filename">ifcfg</code> or JSON format. Note that firewall rules, alias interfaces, and anything that might be tied to the original interface name can break after the renaming because the tool will only change the <code class="filename">ifcfg</code> file, nothing else.
+ </div><div class="para">
+ To see some examples of the command format, issue the following command:
+<pre class="screen">~]$ <code class="command">bond2team --examples</code></pre>
+ New files will be created in a directory whose name starts with <code class="filename">/tmp/bond2team.XXXXXX/</code>, where XXXXXX is a random string. After creating the new configuration files, move the old bonding files to a backup folder and then move the new files to the <code class="filename">/etc/sysconfig/network-scripts/</code> directory.
+ </div><div class="example" id="ex-Convert_a_Bond_to_a_Team"><h6>Example 5.1. Convert a Bond to a Team</h6><div class="example-contents"><div class="para">
+ To convert a current <code class="literal">bond0</code> configuration to team <code class="literal">ifcfg</code>, issue a command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">/usr/bin/bond2team --master bond0</code></pre>
+ Note that this will retain the name <code class="literal">bond0</code>. To use a new name to save the configuration, use the <code class="option">--rename</code> as follows:
+<pre class="screen">~]# <code class="command">/usr/bin/bond2team --master bond0 --rename team0</code></pre>
+ add the <code class="option">--json</code> option to output JSON format files instead of <code class="literal">ifcfg</code> files. See the <code class="filename">teamd.conf(5)</code> man page for examples of JSON format.
+ </div></div></div><br class="example-break" /><div class="example" id="ex_Convert_a_Bond_to_a_Team_and_Specify_the_File_Path"><h6>Example 5.2. Convert a Bond to a Team and Specify the File Path</h6><div class="example-contents"><div class="para">
+ To convert a current <code class="literal">bond0</code> configuration to team <code class="literal">ifcfg</code>, and to manually specify the path to the <code class="literal">ifcfg</code> file, issue a command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">/usr/bin/bond2team --master bond0 --configdir <em class="replaceable"><code>/path/to/ifcfg-file</code></em></code></pre>
+ add the <code class="option">--json</code> option to output JSON format files instead of <code class="literal">ifcfg</code> files.
+ </div></div></div><br class="example-break" /><div class="example" id="ex_Create_a_Team_Configuration_Using_Bond2team"><h6>Example 5.3. Create a Team Configuration Using Bond2team</h6><div class="example-contents"><div class="para">
+ It is also possible to create a team configuration by supplying the <span class="application"><strong>bond2team</strong></span> tool with a list of bonding parameters. For example:
+<pre class="screen">~]# <code class="command">/usr/bin/bond2team --bonding_opts "mode=1 miimon=500"</code></pre>
+ Ports can also be supplied on the command line as follows:
+<pre class="screen">~]# <code class="command">/usr/bin/bond2team --bonding_opts "mode=1 miimon=500 primary=eth1 \</code>
+ <code class="command">primary_reselect-0" --port eth1 --port eth2 --port eth3 --port eth4</code></pre>
+
+ </div></div></div><br class="example-break" /><div class="para">
+ See the <code class="filename">bond2team(1)</code> man page for further details. For an explanation of bonding parameters, see <a class="xref" href="sec-Using_Channel_Bonding.html">Section 4.4, “Using Channel Bonding”</a>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Install_the_Network_Teaming_Daemon.html"><strong>Prev</strong>5.5. Install the Network Teaming Daemon</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team.html"><strong>Next</strong>5.7. Selecting Interfaces to Use as Ports for a N...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Create_a_Channel_Bonding_Interface.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Create_a_Channel_Bonding_Interface.html
new file mode 100644
index 0000000..25b7107
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Create_a_Channel_Bonding_Interface.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.3.2. Create a Channel Bonding Interface</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Network_Bonding_Using_the_Command_Line_Interface.html" title="4.3. Using the Command Line Interface (CLI)" /><link rel="prev" href="sec-Network_Bonding_Using_the_Command_Line_Interface.html" title="4.3. Using the Command Line Interface (CLI)" /><link rel="next" href="sec-Creating_SLAVE_Interfaces.html" title="4.3.3. Creating SLAVE Interfaces" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="p
revious"><a accesskey="p" href="sec-Network_Bonding_Using_the_Command_Line_Interface.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Creating_SLAVE_Interfaces.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Create_a_Channel_Bonding_Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.2. Create a Channel Bonding Interface</h3></div></div></div><div class="para">
+ To create a channel bonding interface, create a file in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory called <code class="filename">ifcfg-bond<em class="replaceable"><code>N</code></em></code>, replacing <em class="replaceable"><code>N</code></em> with the number for the interface, such as <code class="filename">0</code>.
+ </div><div class="para">
+ The contents of the file can be based on a configuration file for whatever type of interface is getting bonded, such as an Ethernet interface. The essential differences are that the <code class="option">DEVICE</code> directive is <code class="option">bond<em class="replaceable"><code>N</code></em></code>, replacing <em class="replaceable"><code>N</code></em> with the number for the interface, and <code class="command">TYPE=Bond</code>. In addition, set <code class="command">BONDING_MASTER=yes</code>.
+ </div><div class="example" id="ex-Example_ifcfg-bond0_Interface_Configuration_File"><h6>Example 4.1. Example ifcfg-bond0 Interface Configuration File</h6><div class="example-contents"><div class="para">
+ An example of a channel bonding interface.
+ </div><pre class="programlisting">DEVICE=bond0
+NAME=bond0
+TYPE=Bond
+BONDING_MASTER=yes
+IPADDR=192.168.1.1
+PREFIX=24
+ONBOOT=yes
+BOOTPROTO=none
+BONDING_OPTS="<em class="replaceable"><code>bonding parameters separated by spaces</code></em>"</pre><div class="para">
+ The NAME directive is useful for naming the connection profile in <span class="application"><strong>NetworkManager</strong></span>. ONBOOT says whether the profile should be started when booting (or more generally, when auto-connecting a device).
+ </div></div></div><br class="example-break" /><div class="important"><div class="admonition_header"><h2>Put all Bonding Module Parameters in ifcfg-bondN Files</h2></div><div class="admonition"><div class="para">
+ Parameters for the bonding kernel module must be specified as a space-separated list in the <code class="option">BONDING_OPTS="<em class="replaceable"><code>bonding parameters</code></em>"</code> directive in the <code class="filename">ifcfg-bond<em class="replaceable"><code>N</code></em></code> interface file. Do <span class="emphasis"><em>not</em></span> specify options for the bonding device in <code class="filename">/etc/modprobe.d/<em class="replaceable"><code>bonding</code></em>.conf</code>, or in the deprecated <code class="filename">/etc/modprobe.conf</code> file.
+ </div><div class="para">
+ The <code class="option">max_bonds</code> parameter is not interface specific and should not be set when using <code class="filename">ifcfg-bond<em class="replaceable"><code>N</code></em></code> files with the <code class="command">BONDING_OPTS</code> directive as this directive will cause the network scripts to create the bond interfaces as required.
+ </div><div class="para">
+ For further instructions and advice on configuring the bonding module and to view the list of bonding parameters, see <a class="xref" href="sec-Using_Channel_Bonding.html">Section 4.4, “Using Channel Bonding”</a>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Network_Bonding_Using_the_Command_Line_Interface.html"><strong>Prev</strong>4.3. Using the Command Line Interface (CLI)</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Creating_SLAVE_Interfaces.html"><strong>Next</strong>4.3.3. Creating SLAVE Interfaces</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Create_a_Network_Bridge.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Create_a_Network_Bridge.html
new file mode 100644
index 0000000..28b2bf2
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Create_a_Network_Bridge.html
@@ -0,0 +1,85 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2.2. Create a Network Bridge</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Network_Bridging_Using_the_Command_Line_Interface.html" title="6.2. Using the Command Line Interface (CLI)" /><link rel="prev" href="sec-Network_Bridging_Using_the_Command_Line_Interface.html" title="6.2. Using the Command Line Interface (CLI)" /><link rel="next" href="sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html" title="6.3. Using the NetworkManager Command Line Tool, nmcli" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png
" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Network_Bridging_Using_the_Command_Line_Interface.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Create_a_Network_Bridge"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.2.2. Create a Network Bridge</h3></div></div></div><div class="para">
+ To create a network bridge, create a file in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory called <code class="filename">ifcfg-br<em class="replaceable"><code>N</code></em></code>, replacing <em class="replaceable"><code>N</code></em> with the number for the interface, such as <code class="filename">0</code>.
+ </div><div class="para">
+ The contents of the file is similar to whatever type of interface is getting bridged to, such as an Ethernet interface. The differences in this example are as follows:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="option">DEVICE</code> directive is given an interface name as its argument in the format <code class="option">br<em class="replaceable"><code>N</code></em></code>, where <em class="replaceable"><code>N</code></em> is replaced with the number of the interface.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">TYPE</code> directive is given an argument <code class="option">Bridge</code> or <code class="option">Ethernet</code>. This directive determines the device type and the argument is case sensitive.
+ </div></li><li class="listitem"><div class="para">
+ The bridge interface configuration file is given an <code class="systemitem">IP</code> address whereas the physical interface configuration file must only have a MAC address (see below).
+ </div></li><li class="listitem"><div class="para">
+ An extra directive, <code class="option">DELAY=0</code>, is added to prevent the bridge from waiting while it monitors traffic, learns where hosts are located, and builds a table of MAC addresses on which to base its filtering decisions. The default delay of 30 seconds is not needed if no routing loops are possible.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="option">NM_CONTROLLED=no</code> should be added to the Ethernet interface to prevent <span class="application"><strong>NetworkManager</strong></span> from altering the file. It can also be added to the bridge configuration file.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The following is a sample bridge interface configuration file using a static <code class="systemitem">IP</code> address:
+ </div><div class="example" id="ex-Sample_ifcfg-br0_Interface_Configuration_File"><h6>Example 6.1. Sample ifcfg-br0 Interface Configuration File</h6><div class="example-contents"><pre class="programlisting">DEVICE=br0
+TYPE=Bridge
+IPADDR=192.168.1.1
+PREFIX=24
+ONBOOT=yes
+BOOTPROTO=none
+NM_CONTROLLED=no
+DELAY=0</pre></div></div><br class="example-break" /><div class="para">
+ To complete the bridge another interface is created, or an existing interface is modified, and pointed to the bridge interface. The following is a sample Ethernet interface configuration file pointing to a bridge interface. Configure your physical interface in <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth<em class="replaceable"><code>X</code></em></code>, where <em class="replaceable"><code>X</code></em> is a unique number corresponding to a specific interface, as follows:
+ </div><div class="example" id="ex-Sample_ifcfg-eth0_Interface_Configuration_File"><h6>Example 6.2. Sample ifcfg-ethX Interface Configuration File</h6><div class="example-contents"><pre class="programlisting">DEVICE=ethX
+TYPE=Ethernet
+HWADDR=AA:BB:CC:DD:EE:FF
+BOOTPROTO=none
+ONBOOT=yes
+NM_CONTROLLED=no
+BRIDGE=br0</pre></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ For the <code class="option">DEVICE</code> directive, almost any interface name could be used as it does not determine the device type. <code class="option">TYPE=Ethernet</code> is not strictly required. If the <code class="option">TYPE</code> directive is not set, the device is treated as an Ethernet device (unless it's name explicitly matches a different interface configuration file.)
+ </div></div></div><div class="para">
+ Specifying the hardware or MAC address using the <code class="command">HWADDR</code> directive will influence the device naming procedure as explained in <a class="xref" href="ch-Consistent_Network_Device_Naming.html">Chapter 8, <em>Consistent Network Device Naming</em></a>.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ If you are configuring bridging on a remote host, and you are connected to that host over the physical NIC you are configuring, please consider the implications of losing connectivity before proceeding. You will lose connectivity when restarting the service and may not be able to regain connectivity if any errors have been made. Console, or out-of-band access is advised.
+ </div></div></div><div class="para">
+ Restart the networking service in order for the changes to take effect. As <code class="systemitem">root</code> issue the following command:
+ </div><pre class="screen">~]# <code class="command">systemctl network restart</code></pre><div class="para">
+ An example of a network bridge formed from two or more bonded Ethernet interfaces will now be given as this is another common application in a virtualization environment. If you are not very familiar with the configuration files for bonded interfaces then please refer to <a class="xref" href="sec-Create_a_Channel_Bonding_Interface.html">Section 4.3.2, “Create a Channel Bonding Interface”</a>
+ </div><div class="para">
+ Create or edit two or more Ethernet interface configuration files, which are to be bonded, as follows:
+<pre class="programlisting">DEVICE=ethX
+TYPE=Ethernet
+SLAVE=yes
+MASTER=bond0
+BOOTPROTO=none
+HWADDR=AA:BB:CC:DD:EE:FF
+NM_CONTROLLED=no</pre>
+
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Using <code class="systemitem">eth<em class="replaceable"><code>X</code></em></code> as the interface name is common practice but almost any name could be used.
+ </div></div></div><div class="para">
+ Create or edit one interface configuration file, <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond0</code>, as follows:
+<pre class="programlisting">DEVICE=bond0
+ONBOOT=yes
+BONDING_OPTS='mode=1 miimon=100'
+BRIDGE=brbond0
+NM_CONTROLLED=no</pre>
+
+ </div><div class="para">
+ Create or edit one interface configuration file, <code class="filename">/etc/sysconfig/network-scripts/ifcfg-brbond0</code>, as follows:
+<pre class="programlisting">DEVICE=brbond0
+ONBOOT=yes
+TYPE=Bridge
+IPADDR=192.168.1.1
+PREFIX=24
+NM_CONTROLLED=no</pre>
+
+ </div><div class="para">
+ We now have two or more interface configuration files with the <code class="option">MASTER=bond0</code> directive. These point to the configuration file named <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond0</code>, which contains the <code class="option">DEVICE=bond0</code> directive. This <code class="filename">ifcfg-bond0</code> in turn points to the <code class="filename">/etc/sysconfig/network-scripts/ifcfg-brbond0</code> configuration file, which contains the <code class="systemitem">IP</code> address, and acts as an interface to the virtual networks inside the host.
+ </div><div class="para">
+ Restart the networking service, in order for the changes to take effect. As <code class="systemitem">root</code> issue the following command:
+ </div><pre class="screen">~]# <code class="command">systemctl network restart</code></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Network_Bridging_Using_the_Command_Line_Interface.html"><strong>Prev</strong>6.2. Using the Command Line Interface (CLI)</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html"><strong>Next</strong>6.3. Using the NetworkManager Command Line Tool, ...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Creating_Multiple_Bonds.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Creating_Multiple_Bonds.html
new file mode 100644
index 0000000..88ce256
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Creating_Multiple_Bonds.html
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.3.5. Creating Multiple Bonds</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Network_Bonding_Using_the_Command_Line_Interface.html" title="4.3. Using the Command Line Interface (CLI)" /><link rel="prev" href="sec-Activating_a_Channel_Bond.html" title="4.3.4. Activating a Channel Bond" /><link rel="next" href="sec-Using_Channel_Bonding.html" title="4.4. Using Channel Bonding" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Activati
ng_a_Channel_Bond.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_Channel_Bonding.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Creating_Multiple_Bonds"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.5. Creating Multiple Bonds</h3></div></div></div><div class="para">
+ In Fedora 20, for each bond a channel bonding interface is created including the <code class="command">BONDING_OPTS</code> directive. This configuration method is used so that multiple bonding devices can have different configurations. To create multiple channel bonding interfaces, proceed as follows:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Create multiple <code class="filename">ifcfg-bond<em class="replaceable"><code>N</code></em></code> files with the <code class="command">BONDING_OPTS</code> directive; this directive will cause the network scripts to create the bond interfaces as required.
+ </div></li><li class="listitem"><div class="para">
+ Create, or edit existing, interface configuration files to be bonded and include the <code class="command">SLAVE</code> directive.
+ </div></li><li class="listitem"><div class="para">
+ Assign the interfaces to be bonded, the slave interfaces, to the channel bonding interfaces by means of the <code class="command">MASTER</code> directive.
+ </div></li></ul></div>
+
+ </div><div class="example" id="ex-Example-multiple-bondN_interface_configuration_files"><h6>Example 4.3. Example multiple ifcfg-bondN interface configuration files</h6><div class="example-contents"><div class="para">
+ The following is an example of a channel bonding interface configuration file:
+<pre class="programlisting">DEVICE=bondN
+NAME=bondN
+TYPE=Bond
+BONDING_MASTER=yes
+IPADDR=192.168.1.1
+PREFIX=24
+ONBOOT=yes
+BOOTPROTO=none
+BONDING_OPTS="<em class="replaceable"><code>bonding parameters separated by spaces</code></em>"</pre>
+ </div><div class="para">
+ In this example, replace <em class="replaceable"><code>N</code></em> with the number for the bond interface. For example, to create two bonds create two configuration files, <code class="filename">ifcfg-bond0</code> and <code class="filename">ifcfg-bond1</code>, with appropriate <code class="systemitem">IP</code> addresses.
+ </div></div></div><br class="example-break" /><div class="para">
+ Create the interfaces to be bonded as per <a class="xref" href="sec-Creating_SLAVE_Interfaces.html#ex-Example_Slave_Interface_Configuration_File">Example 4.2, “Example Slave Interface Configuration File”</a> and assign them to the bond interfaces as required using the <code class="command">MASTER=bond<em class="replaceable"><code>N</code></em></code> directive. For example, continuing on from the example above, if two interfaces per bond are required, then for two bonds create four interface configuration files and assign the first two using <code class="command">MASTER=bond<em class="replaceable"><code>0</code></em></code> and the next two using <code class="command">MASTER=bond<em class="replaceable"><code>1</code></em></code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Activating_a_Channel_Bond.html"><strong>Prev</strong>4.3.4. Activating a Channel Bond</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_Channel_Bonding.html"><strong>Next</strong>4.4. Using Channel Bonding</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Creating_SLAVE_Interfaces.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Creating_SLAVE_Interfaces.html
new file mode 100644
index 0000000..79cc82d
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Creating_SLAVE_Interfaces.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.3.3. Creating SLAVE Interfaces</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Network_Bonding_Using_the_Command_Line_Interface.html" title="4.3. Using the Command Line Interface (CLI)" /><link rel="prev" href="sec-Create_a_Channel_Bonding_Interface.html" title="4.3.2. Create a Channel Bonding Interface" /><link rel="next" href="sec-Activating_a_Channel_Bond.html" title="4.3.4. Activating a Channel Bond" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a acce
sskey="p" href="sec-Create_a_Channel_Bonding_Interface.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Activating_a_Channel_Bond.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Creating_SLAVE_Interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.3. Creating SLAVE Interfaces</h3></div></div></div><div class="para">
+ The channel bonding interface is the <span class="quote">“<span class="quote">master</span>”</span> and the interfaces to be bonded are referred to as the <span class="quote">“<span class="quote">slaves</span>”</span>. After the channel bonding interface is created, the network interfaces to be bound together must be configured by adding the <code class="option">MASTER</code> and <code class="option">SLAVE</code> directives to the configuration files of the slaves. The configuration files for each of the slave interfaces can be nearly identical.
+ </div><div class="example" id="ex-Example_Slave_Interface_Configuration_File"><h6>Example 4.2. Example Slave Interface Configuration File</h6><div class="example-contents"><div class="para">
+ For example, if two Ethernet interfaces are being channel bonded, <code class="literal">eth0</code> and <code class="literal">eth1</code>, they can both look like the following example:
+ </div><pre class="programlisting">DEVICE=eth<em class="replaceable"><code>N</code></em>
+NAME=bond0-slave
+TYPE=Ethernet
+BOOTPROTO=none
+ONBOOT=yes
+MASTER=bond0
+SLAVE=yes</pre><div class="para">
+ In this example, replace <em class="replaceable"><code>N</code></em> with the numerical value for the interface. Note that if more than one profile or configuration file exists with ONBOOT=yes for an interface, they may race with each other and a plain TYPE=Ethernet profile may be activated instead of a bond slave.
+ </div></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Create_a_Channel_Bonding_Interface.html"><strong>Prev</strong>4.3.2. Create a Channel Bonding Interface</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Activating_a_Channel_Bond.html"><strong>Next</strong>4.3.4. Activating a Channel Bond</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Creating_a_Bond_Connection_Using_a_GUI.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Creating_a_Bond_Connection_Using_a_GUI.html
new file mode 100644
index 0000000..7322f2d
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Creating_a_Bond_Connection_Using_a_GUI.html
@@ -0,0 +1,101 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2. Creating a Bond Connection Using a GUI</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Bonding.html" title="Chapter 4. Configure Network Bonding" /><link rel="prev" href="ch-Configure_Network_Bonding.html" title="Chapter 4. Configure Network Bonding" /><link rel="next" href="sec-Network_Bonding_Using_the_Command_Line_Interface.html" title="4.3. Using the Command Line Interface (CLI)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p"
href="ch-Configure_Network_Bonding.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Bonding_Using_the_Command_Line_Interface.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Creating_a_Bond_Connection_Using_a_GUI"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Creating a Bond Connection Using a GUI</h2></div></div></div><div class="para">
+ You can use the GNOME <span class="application"><strong>control-center</strong></span> utility to direct <span class="application"><strong>NetworkManager</strong></span> to create a Bond from two or more Wired or InfiniBand connections. It is not necessary to create the connections to be bonded first. They can be configured as part of the process to configure the bond. You must have the MAC addresses of the interfaces available in order to complete the configuration process.
+ </div><div class="section" id="sec-Establishing_a_Bond_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.2.1. Establishing a Bond Connection</h3></div></div></div><div class="procedure" id="procedure-Adding_a_New_Bond_Connection"><h6>Procedure 4.1. Adding a New Bond Connection</h6><div class="para">
+ You can configure a Bond connection by opening the <span class="guilabel"><strong>Network</strong></span> window, clicking the plus symbol, and selecting <span class="guilabel"><strong>Bond</strong></span> from the list.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Click the plus symbol to open the selection list. Select <span class="guilabel"><strong>Bond</strong></span>. The <span class="guilabel"><strong>Editing Bond connection <em class="replaceable"><code>1</code></em></strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ On the <span class="guilabel"><strong>Bond</strong></span> tab, click <span class="guibutton"><strong>Add</strong></span> and select the type of interface you want to use with the bond connection. Click the <span class="guibutton"><strong>Create</strong></span> button. Note that the dialog to select the slave type only comes up when you create the first slave; after that, it will automatically use that same type for all further slaves.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Editing bond0 slave 1</strong></span> window appears. Use the <span class="guilabel"><strong>Device MAC address</strong></span> drop-down menu to select the MAC address of the interface to be bonded. The first slave's MAC address will be used as the MAC address for the bond interface. If required, enter a clone MAC address to be used as the bond's MAC address. Click the <span class="guibutton"><strong>Save</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ The name of the bonded slave appears in the <span class="guilabel"><strong>Bonded connections</strong></span> window. Click the <span class="guibutton"><strong>Add</strong></span> button to add further slave connections.
+ </div></li><li class="step"><div class="para">
+ Review and confirm the settings and then click the <span class="guilabel"><strong>Save</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Edit the bond-specific settings by referring to <a class="xref" href="sec-Creating_a_Bond_Connection_Using_a_GUI.html#sec-Configuring_the_Bond_Tab">Section 4.2.1.1, “Configuring the Bond Tab”</a> below.
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_Bond_Connection"><h6>Procedure 4.2. Editing an Existing Bond Connection</h6><div class="para">
+ Follow these steps to edit an existing bond connection.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the connection you want to edit and click the <span class="guilabel"><strong>Options</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>General</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Configure the connection name, auto-connect behavior, and availability settings.
+ </div><div class="para">
+ Five settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types, see the <span class="guilabel"><strong>General</strong></span> tab:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the menu of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to this network when it is available</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>All users may connect to this network</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="sec-System-wide_and_Private_Connection_Profiles.html">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to VPN when using this connection</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to a VPN connection when it is available. Select the VPN from the drop-down menu.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Firewall Zone</strong></span> — Select the firewall zone from the drop-down menu.
+ </div></li></ul></div></li><li class="step"><div class="para">
+ Edit the bond-specific settings by referring to <a class="xref" href="sec-Creating_a_Bond_Connection_Using_a_GUI.html#sec-Configuring_the_Bond_Tab">Section 4.2.1.1, “Configuring the Bond Tab”</a> below.
+ </div></li></ol></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-bond">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your bond connection, click the <span class="guibutton"><strong>Save</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network</strong></span> window and clicking <span class="guilabel"><strong>Options</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv6</code> settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv6_Settings">Section 2.2.10.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div><div class="section" id="sec-Configuring_the_Bond_Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">4.2.1.1. Configuring the Bond Tab</h4></div></div></div><div class="para">
+ If you have already added a new bond connection (refer to <a class="xref" href="sec-Creating_a_Bond_Connection_Using_a_GUI.html#procedure-Adding_a_New_Bond_Connection">Procedure 4.1, “Adding a New Bond Connection”</a> for instructions), you can edit the <span class="guilabel"><strong>Bond</strong></span> tab to set the load sharing mode and the type of link monitoring to use to detect failures of a slave connection.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Mode</strong></span> </span></dt><dd><div class="para">
+ The mode that is used to share traffic over the slave connections which make up the bond. The default is <span class="guilabel"><strong>Round-robin</strong></span>. Other load sharing modes, such as <code class="systemitem">802.3ad</code>, can be selected by means of the drop-down list.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Link Monitoring</strong></span> </span></dt><dd><div class="para">
+ The method of monitoring the slaves ability to carry network traffic.
+ </div></dd></dl></div><div class="para">
+ The following modes of load sharing are selectable from the <span class="guilabel"><strong>Mode</strong></span> drop-down list:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Round-robin</strong></span> </span></dt><dd><div class="para">
+ Sets a round-robin policy for fault tolerance and load balancing. Transmissions are received and sent out sequentially on each bonded slave interface beginning with the first one available. This mode might not work behind a bridge with virtual machines without additional switch configuration.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Active backup</strong></span> </span></dt><dd><div class="para">
+ Sets an active-backup policy for fault tolerance. Transmissions are received and sent out via the first available bonded slave interface. Another bonded slave interface is only used if the active bonded slave interface fails. Note that this is the only mode available for bonds of InfiniBand devices.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>XOR</strong></span> </span></dt><dd><div class="para">
+ Sets an XOR (exclusive-or) policy. Transmissions are based on the selected hash policy. The default is to derive a hash by XOR of the source and destination MAC addresses multiplied by the modulo of the number of slave interfaces. In this mode traffic destined for specific peers will always be sent over the same interface. As the destination is determined by the MAC addresses this method works best for traffic to peers on the same link or local network. If traffic has to pass through a single router then this mode of traffic balancing will be suboptimal.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Broadcast</strong></span> </span></dt><dd><div class="para">
+ Sets a broadcast policy for fault tolerance. All transmissions are sent on all slave interfaces. This mode might not work behind a bridge with virtual machines without additional switch configuration.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>802.3ad</strong></span> </span></dt><dd><div class="para">
+ Sets an IEEE <code class="systemitem">802.3ad</code> dynamic link aggregation policy. Creates aggregation groups that share the same speed and duplex settings. Transmits and receives on all slaves in the active aggregator. Requires a network switch that is <code class="systemitem">802.3ad</code> compliant.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Adaptive transmit load balancing</strong></span> </span></dt><dd><div class="para">
+ Sets an adaptive Transmit Load Balancing (TLB) policy for fault tolerance and load balancing. The outgoing traffic is distributed according to the current load on each slave interface. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed slave. This mode is only suitable for local addresses known to the kernel bonding module and therefore cannot be used behind a bridge with virtual machines.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Adaptive load balancing</strong></span> </span></dt><dd><div class="para">
+ Sets an Adaptive Load Balancing (ALB) policy for fault tolerance and load balancing. Includes transmit and receive load balancing for <code class="systemitem">IPv4</code> traffic. Receive load balancing is achieved through <code class="systemitem">ARP</code> negotiation. This mode is only suitable for local addresses known to the kernel bonding module and therefore cannot be used behind a bridge with virtual machines.
+ </div></dd></dl></div><div class="para">
+ The following types of link monitoring can be selected from the <span class="guilabel"><strong>Link Monitoring</strong></span> drop-down list. It is a good idea to test which channel bonding module parameters work best for your bonded interfaces.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>MII (Media Independent Interface)</strong></span> </span></dt><dd><div class="para">
+ The state of the carrier wave of the interface is monitored. This can be done by querying the driver, by querying MII registers directly, or by using <span class="application"><strong>ethtool</strong></span> to query the device. Three options are available:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Monitoring Frequency</strong></span> </span></dt><dd><div class="para">
+ The time interval, in milliseconds, between querying the driver or MII registers.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Link up delay</strong></span> </span></dt><dd><div class="para">
+ The time in milliseconds to wait before attempting to use a link that has been reported as up. This delay can be used if some gratuitous <code class="systemitem">ARP</code> requests are lost in the period immediately following the link being reported as <span class="quote">“<span class="quote">up</span>”</span>. This can happen during switch initialization for example.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Link down delay</strong></span> </span></dt><dd><div class="para">
+ The time in milliseconds to wait before changing to another link when a previously active link has been reported as <span class="quote">“<span class="quote">down</span>”</span>. This delay can be used if an attached switch takes a relatively long time to change to backup mode.
+ </div></dd></dl></div></dd></dl></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>ARP</strong></span> </span></dt><dd><div class="para">
+ The address resolution protocol (<code class="systemitem">ARP</code>) is used to probe one or more peers to determine how well the link-layer connections are working. It is dependent on the device driver providing the transmit start time and the last receive time.
+ </div><div class="para">
+ Two options are available:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Monitoring Frequency</strong></span> </span></dt><dd><div class="para">
+ The time interval, in milliseconds, between sending <code class="systemitem">ARP</code> requests.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>ARP targets</strong></span> </span></dt><dd><div class="para">
+ A comma separated list of <code class="systemitem">IP</code> addresses to send <code class="systemitem">ARP</code> requests to.
+ </div></dd></dl></div></dd></dl></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Configure_Network_Bonding.html"><strong>Prev</strong>Chapter 4. Configure Network Bonding</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Bonding_Using_the_Command_Line_Interface.html"><strong>Next</strong>4.3. Using the Command Line Interface (CLI)</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Creating_a_Network_Team_Using_a_GUI.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Creating_a_Network_Team_Using_a_GUI.html
new file mode 100644
index 0000000..8390376
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Creating_a_Network_Team_Using_a_GUI.html
@@ -0,0 +1,71 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9. Creating a Network Team Using a GUI</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Teaming.html" title="Chapter 5. Configure Network Teaming" /><link rel="prev" href="sec-Selecting_Network_Team_Configuration_Methods.html" title="5.8. Selecting Network Team Configuration Methods" /><link rel="next" href="sec-Configure_a_Network_Team_Using-the_Command_Line.html" title="5.10. Configure a Network Team Using the Command Line" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docna
v"><li class="previous"><a accesskey="p" href="sec-Selecting_Network_Team_Configuration_Methods.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_a_Network_Team_Using-the_Command_Line.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Creating_a_Network_Team_Using_a_GUI"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.9. Creating a Network Team Using a GUI</h2></div></div></div><div class="section" id="sec-Establishing_a_Team_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.1. Establishing a Team Connection</h3></div></div></div><div class="para">
+ You can use the GNOME <span class="application"><strong>control-center</strong></span> utility to direct <span class="application"><strong>NetworkManager</strong></span> to create a team from two or more Wired or InfiniBand connections. It is not necessary to create the connections to be teamed first. They can be configured as part of the process to configure the team. You must have the MAC addresses of the interfaces available in order to complete the configuration process.
+ </div><div class="procedure" id="procedure-Adding_a_New_Team_Connection"><h6>Procedure 5.1. Adding a New Team Connection</h6><div class="para">
+ You can configure a team connection by opening the <span class="guilabel"><strong>Network</strong></span> window, clicking the plus symbol, and selecting <span class="guilabel"><strong>Team</strong></span> from the list.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Click the plus symbol to open the selection list. Select <span class="guilabel"><strong>Team</strong></span>. The <span class="guilabel"><strong>Editing Team Connection <em class="replaceable"><code>1</code></em></strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ On the <span class="guilabel"><strong>Team</strong></span> tab, click <span class="guibutton"><strong>Add</strong></span> and select the type of interface you want to use with the team connection. Click the <span class="guibutton"><strong>Create</strong></span> button. Note that the dialog to select the port type only comes up when you create the first port; after that, it will automatically use that same type for all further ports.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Editing team0 port 1</strong></span> window appears. Fill in the MAC address of the first interface to be added to the team.
+ </div></li><li class="step"><div class="para">
+ If custom port settings are to be applied, click on the <span class="guilabel"><strong>Team Port</strong></span> tab and enter a JSON configuration string or import it from a file.
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guibutton"><strong>Save</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ The name of the teamed port appears in the <span class="guilabel"><strong>Teamed connections</strong></span> window. Click the <span class="guibutton"><strong>Add</strong></span> button to add further port connections.
+ </div></li><li class="step"><div class="para">
+ Review and confirm the settings and then click the <span class="guilabel"><strong>Save</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Edit the team-specific settings by referring to <a class="xref" href="sec-Creating_a_Network_Team_Using_a_GUI.html#sec-Configuring_the_Team_Tab">Section 5.9.1.1, “Configuring the Team Tab”</a> below.
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_Team_Connection"><h6>Procedure 5.2. Editing an Existing Team Connection</h6><div class="para">
+ Follow these steps to edit an existing bond connection.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the connection you want to edit and click the <span class="guilabel"><strong>Options</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>General</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Configure the connection name, auto-connect behavior, and availability settings.
+ </div><div class="para">
+ Five settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types, see the <span class="guilabel"><strong>General</strong></span> tab:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the menu of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to this network when it is available</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>All users may connect to this network</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="sec-System-wide_and_Private_Connection_Profiles.html">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to VPN when using this connection</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to a VPN connection when it is available. Select the VPN from the drop-down menu.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Firewall Zone</strong></span> — Select the firewall zone from the drop-down menu.
+ </div></li></ul></div></li><li class="step"><div class="para">
+ Edit the team-specific settings by referring to <a class="xref" href="sec-Creating_a_Network_Team_Using_a_GUI.html#sec-Configuring_the_Team_Tab">Section 5.9.1.1, “Configuring the Team Tab”</a> below.
+ </div></li></ol></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-team">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your team connection, click the <span class="guibutton"><strong>Save</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network</strong></span> window and clicking <span class="guilabel"><strong>Options</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ IPv6 settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv6_Settings">Section 2.2.10.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div><div class="section" id="sec-Configuring_the_Team_Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">5.9.1.1. Configuring the Team Tab</h4></div></div></div><div class="para">
+ If you have already added a new team connection you can enter a custom JSON configuration string in the text box or import a configuration file. Click <span class="guilabel"><strong>Save</strong></span> to apply the JSON configuration to the team interface.
+ </div><div class="para">
+ For examples of JSON strings, see <a class="xref" href="sec-Configure_teamd_Runners.html">Section 5.12, “Configure teamd Runners”</a>
+ </div><div class="para">
+ See <a class="xref" href="sec-Creating_a_Network_Team_Using_a_GUI.html#procedure-Adding_a_New_Team_Connection">Procedure 5.1, “Adding a New Team Connection”</a> for instructions on how to add a new team.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Selecting_Network_Team_Configuration_Methods.html"><strong>Prev</strong>5.8. Selecting Network Team Configuration Methods</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_a_Network_Team_Using-the_Command_Line.html"><strong>Next</strong>5.10. Configure a Network Team Using the Command ...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Creating_a_Network_Team_Using_ifcfg_Files.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Creating_a_Network_Team_Using_ifcfg_Files.html
new file mode 100644
index 0000000..871cdaa
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Creating_a_Network_Team_Using_ifcfg_Files.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.2. Creating a Network Team Using ifcfg Files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_a_Network_Team_Using-the_Command_Line.html" title="5.10. Configure a Network Team Using the Command Line" /><link rel="prev" href="sec-Configure_a_Network_Team_Using-the_Command_Line.html" title="5.10. Configure a Network Team Using the Command Line" /><link rel="next" href="sec-Add_a_port_to_a_Network_Team_Using_iputils.html" title="5.10.3. Add a Port to a Network Team Using iputils" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Document
ation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_a_Network_Team_Using-the_Command_Line.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Add_a_port_to_a_Network_Team_Using_iputils.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Creating_a_Network_Team_Using_ifcfg_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.2. Creating a Network Team Using ifcfg Files</h3></div></div></div><div class="para">
+ To create a networking team using <code class="literal">ifcfg</code> files, create a file in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory as follows:
+<pre class="screen">DEVICE=team0
+DEVICETYPE=Team
+ONBOOT=yes
+BOOTPROTO=none
+IPADDR=192.168.11.1
+PREFIX=24
+TEAM_CONFIG='{"runner": {"name": "activebackup"}, "link_watch": {"name": "ethtool"}}'</pre>
+ This creates the interface to the team, in other words, this is the master.
+ </div><div class="para">
+ To create a port to be a member of <span class="interface">team0</span>, create one or more files in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory as follows:
+<pre class="screen">DEVICE=eth1
+HWADDR=D4:85:64:01:46:9E
+DEVICETYPE=TeamPort
+ONBOOT=yes
+TEAM_MASTER=team0
+TEAM_PORT_CONFIG='{"prio": 100}'</pre>
+ Add additional port interfaces similar to the above as required, changing the DEVICE and HWADDR field to match the ports (the network devices) being added. If port priority is not specified by <code class="literal">prio</code> it defaults to <code class="literal">0</code>; it accepts negative and positive values in the range <code class="literal">-32,767</code> to <code class="literal">+32,767</code>.
+ </div><div class="para">
+ Specifying the hardware or MAC address using the <code class="command">HWADDR</code> directive will influence the device naming procedure. This is explained in <a class="xref" href="ch-Consistent_Network_Device_Naming.html">Chapter 8, <em>Consistent Network Device Naming</em></a>.
+ </div><div class="para">
+ To bring up the network team, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">ifup team0</code></pre>
+ To view the network team, issue the following command:
+<pre class="screen">~]$ <code class="command">ip link show</code></pre>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_a_Network_Team_Using-the_Command_Line.html"><strong>Prev</strong>5.10. Configure a Network Team Using the Command ...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Add_a_port_to_a_Network_Team_Using_iputils.html"><strong>Next</strong>5.10.3. Add a Port to a Network Team Using iputils</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Disabling_Consistent_Network_Device_Naming.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Disabling_Consistent_Network_Device_Naming.html
new file mode 100644
index 0000000..01ce9d7
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Disabling_Consistent_Network_Device_Naming.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.9. Disabling Consistent Network Device Naming</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Consistent_Network_Device_Naming.html" title="Chapter 8. Consistent Network Device Naming" /><link rel="prev" href="sec-Controlling_the_Selection_of_Network_Device_Names.html" title="8.8. Controlling the Selection of Network Device Names" /><link rel="next" href="sec_Troubleshooting_Network_Device_Naming.html" title="8.10. Troubleshooting Network Device Naming" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="d
ocnav"><li class="previous"><a accesskey="p" href="sec-Controlling_the_Selection_of_Network_Device_Names.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec_Troubleshooting_Network_Device_Naming.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Disabling_Consistent_Network_Device_Naming"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.9. Disabling Consistent Network Device Naming</h2></div></div></div><div class="para">
+ To disable consistent network device naming, choose from one of the following:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Disable the assignment of fixed names, so that the unpredictable kernel names are used again, by masking <span class="application"><strong>udev</strong></span>'s rule file for the default policy. This <span class="quote">“<span class="quote">masking</span>”</span> can be done by making a symbolic link to <code class="filename">/dev/null</code>. As <code class="systemitem">root</code>, issue a command as follows:
+<pre class="screen">~]# <code class="command">ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules</code></pre>
+
+ </div></li><li class="listitem"><div class="para">
+ Create your own manual naming scheme, for example by naming your interfaces <span class="quote">“<span class="quote">internet0</span>”</span>, <span class="quote">“<span class="quote">dmz0</span>”</span> or <span class="quote">“<span class="quote">lan0</span>”</span>. To do that create your own <span class="application"><strong>udev</strong></span> rules file and set the NAME property for the devices. Make sure to order it before the default policy file, for example by naming it <code class="filename">/etc/udev/rules.d/70-my-net-names.rules</code>.
+ </div></li><li class="listitem"><div class="para">
+ Alter the default policy file to pick a different naming scheme, for example to name all interfaces after their MAC address by default. As <code class="systemitem">root</code> copy the default policy file as follows:
+<pre class="screen">~]# <code class="command">cp /usr/lib/udev/rules.d/80-net-name-slot.rules /etc/udev/rules.d/80-net-name-slot.rules</code></pre>
+ Edit the file in the <code class="filename">/etc/udev/rules.d/</code> directory and change the lines as necessary.
+ </div></li><li class="listitem"><div class="para">
+ Add the following line to the <code class="filename">/etc/default/grub</code> file: <pre class="synopsis">net.ifnames=0</pre> or pass it to the kernel at boot time using the GRUB2 command-line interface. For more information about GRUB2 see <em class="citetitle">Fedora 20 System Administrator's Guide</em>.
+ </div></li></ul></div>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Controlling_the_Selection_of_Network_Device_Names.html"><strong>Prev</strong>8.8. Controlling the Selection of Network Device ...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec_Troubleshooting_Network_Device_Naming.html"><strong>Next</strong>8.10. Troubleshooting Network Device Naming</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Establishing_a_DSL_Connection.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Establishing_a_DSL_Connection.html
new file mode 100644
index 0000000..4649a30
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Establishing_a_DSL_Connection.html
@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.9. Establishing a DSL Connection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html" title="2.2. Using NetworkManager with the GNOME Graphical User Interface" /><link rel="prev" href="sec-Establishing_a_Mobile_Broadband_Connection.html" title="2.2.8. Establishing a Mobile Broadband Connection" /><link rel="next" href="sec-Configuring_Connection_Settings.html" title="2.2.10. Configuring Connection Settings" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation
Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_a_Mobile_Broadband_Connection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Connection_Settings.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Establishing_a_DSL_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.9. Establishing a DSL Connection</h3></div></div></div><div class="para">
+ This section is intended for those installations which have a DSL card fitted within a host rather than the external combined DSL modem router combinations typical of private consumer or SOHO installations.
+ </div><div class="procedure" id="procedure-Adding_a_New_DSL_Connection"><h6>Procedure 2.7. Adding a New DSL Connection</h6><div class="para">
+ You can configure a new DSL connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> window, clicking the <span class="guibutton"><strong>Add</strong></span> button and selecting <span class="guilabel"><strong>DSL</strong></span> from the <span class="guilabel"><strong>Hardware</strong></span> section of the new connection list.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">nm-connection-editor</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network Connections</strong></span> tool appears.
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guibutton"><strong>Add</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Choose a Connection Type</strong></span> list appears.
+ </div></li><li class="step"><div class="para">
+ Select <span class="guimenu"><strong>DSL</strong></span> and press the <span class="guibutton"><strong>Create</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Editing DSL Connection <em class="replaceable"><code>1</code></em></strong></span> window appears.
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_DSL_Connection"><h6>Procedure 2.8. Editing an Existing DSL Connection</h6><div class="para">
+ You can configure an existing DSL connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> window and selecting the name of the connection from the list. Then click the <span class="guibutton"><strong>Edit</strong></span> button.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">nm-connection-editor</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network Connections</strong></span> tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the connection you want to edit and click the <span class="guilabel"><strong>Edit</strong></span> button.
+ </div></li></ol></div><h4 id="bh-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-dsl">Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Five settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types, see the <span class="guilabel"><strong>General</strong></span> tab:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the menu of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to this network when it is available</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>All users may connect to this network</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="sec-System-wide_and_Private_Connection_Profiles.html">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to VPN when using this connection</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to a VPN connection when it is available. Select the VPN from the drop-down menu.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Firewall Zone</strong></span> — Select the Firewall Zone from the drop-down menu.
+ </div></li></ul></div><h4 id="bh-Configuring_the_DSL_Tab">Configuring the DSL Tab</h4><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the user name used to authenticate with the service provider.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Service</strong></span> </span></dt><dd><div class="para">
+ Leave blank unless otherwise directed by your service provider.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password supplied by the service provider.
+ </div></dd></dl></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-DSL">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your DSL connection, click the <span class="guibutton"><strong>Apply</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>The MAC address and MTU</strong></span> settings, click the <span class="guilabel"><strong>Wired</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_a_Wired_Ethernet_Connection.html#sec-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-wired">Section 2.2.5.1, “Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings”</a>;
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Point-to-point</strong></span> settings for the connection, click the <span class="guilabel"><strong>PPP Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_PPP_Point-to-Point_Settings">Section 2.2.10.3, “Configuring PPP (Point-to-Point) Settings”</a>;
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_a_Mobile_Broadband_Connection.html"><strong>Prev</strong>2.2.8. Establishing a Mobile Broadband Connection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Connection_Settings.html"><strong>Next</strong>2.2.10. Configuring Connection Settings</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Establishing_a_Mobile_Broadband_Connection.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Establishing_a_Mobile_Broadband_Connection.html
new file mode 100644
index 0000000..8ea82b4
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Establishing_a_Mobile_Broadband_Connection.html
@@ -0,0 +1,107 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.8. Establishing a Mobile Broadband Connection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html" title="2.2. Using NetworkManager with the GNOME Graphical User Interface" /><link rel="prev" href="sec-Establishing_a_VPN_Connection.html" title="2.2.7. Establishing a VPN Connection" /><link rel="next" href="sec-Establishing_a_DSL_Connection.html" title="2.2.9. Establishing a DSL Connection" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docn
av"><li class="previous"><a accesskey="p" href="sec-Establishing_a_VPN_Connection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_a_DSL_Connection.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Establishing_a_Mobile_Broadband_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.8. Establishing a Mobile Broadband Connection</h3></div></div></div><div class="para">
+ You can use <span class="application"><strong>NetworkManager</strong></span>'s mobile broadband connection abilities to connect to the following <em class="firstterm">2G</em> and <em class="firstterm">3G</em> services:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 2G — <em class="firstterm">GPRS</em> (<em class="firstterm">General Packet Radio Service</em>), <em class="firstterm">EDGE</em> (<em class="firstterm">Enhanced Data Rates for GSM Evolution</em>), or CDMA (Code Division Multiple Access).
+ </div></li><li class="listitem"><div class="para">
+ 3G — <em class="firstterm">UMTS</em> (<em class="firstterm">Universal Mobile Telecommunications System</em>), <em class="firstterm">HSPA</em> (<em class="firstterm">High Speed Packet Access</em>), or EVDO (EVolution Data-Only).
+ </div></li></ul></div><div class="para">
+ Your computer must have a mobile broadband device (modem), which the system has discovered and recognized, in order to create the connection. Such a device may be built into your computer (as is the case on many notebooks and netbooks), or may be provided separately as internal or external hardware. Examples include PC card, USB Modem or Dongle, mobile or cellular telephone capable of acting as a modem.
+ </div><div class="procedure" id="procedure-Adding_a_New_Mobile_Broadband_Connection"><h6>Procedure 2.5. Adding a New Mobile Broadband Connection</h6><div class="para">
+ You can configure a mobile broadband connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> tool and selecting the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">nm-connection-editor</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network Connections</strong></span> tool appears.
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guibutton"><strong>Add</strong></span> button. The <span class="guilabel"><strong>Choose a Connection Type</strong></span> menu opens.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guimenu"><strong>Mobile Broadband</strong></span> menu entry.
+ </div></li><li class="step"><div class="para">
+ Click <span class="guibutton"><strong>Create</strong></span> to open the <span class="guilabel"><strong>Set up a Mobile Broadband Connection</strong></span> assistant.
+ </div></li><li class="step"><div class="para">
+ Under <span class="guilabel"><strong>Create a connection for this mobile broadband device</strong></span>, choose the 2G- or 3G-capable device you want to use with the connection. If the drop-down menu is inactive, this indicates that the system was unable to detect a device capable of mobile broadband. In this case, click <span class="guilabel"><strong>Cancel</strong></span>, ensure that you do have a mobile broadband-capable device attached and recognized by the computer and then retry this procedure. Click the <span class="guilabel"><strong>Continue</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select the country where your service provider is located from the list and click the <span class="guilabel"><strong>Continue</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select your provider from the list or enter it manually. Click the <span class="guilabel"><strong>Continue</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Select your payment plan from the drop-down menu and confirm the <em class="firstterm">Access Point Name</em> (<acronym class="acronym">APN</acronym>) is correct. Click the <span class="guilabel"><strong>Continue</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Review and confirm the settings and then click the <span class="guilabel"><strong>Apply</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Edit the mobile broadband-specific settings by referring to <a class="xref" href="sec-Establishing_a_Mobile_Broadband_Connection.html#sec-Configuring_the_Mobile_Broadband_Tab">Section 2.2.8.1, “Configuring the Mobile Broadband Tab”</a>.
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_Mobile_Broadband_Connection"><h6>Procedure 2.6. Editing an Existing Mobile Broadband Connection</h6><div class="para">
+ Follow these steps to edit an existing mobile broadband connection.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">nm-connection-editor</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network Connections</strong></span> tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab.
+ </div></li><li class="step"><div class="para">
+ Select the connection you want to edit and click the <span class="guilabel"><strong>Edit</strong></span> button.
+ </div></li><li class="step"><div class="para">
+ Configure the connection name, auto-connect behavior, and availability settings.
+ </div><div class="para">
+ Five settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types, see the <span class="guilabel"><strong>General</strong></span> tab:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the menu of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to this network when it is available</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>All users may connect to this network</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="sec-System-wide_and_Private_Connection_Profiles.html">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to VPN when using this connection</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to a VPN connection when it is available. Select the VPN from the drop-down menu.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Firewall Zone</strong></span> — Select the Firewall Zone from the drop-down menu.
+ </div></li></ul></div></li><li class="step"><div class="para">
+ Edit the mobile broadband-specific settings by referring to <a class="xref" href="sec-Establishing_a_Mobile_Broadband_Connection.html#sec-Configuring_the_Mobile_Broadband_Tab">Section 2.2.8.1, “Configuring the Mobile Broadband Tab”</a>.
+ </div></li></ol></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-mobile_broadband">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your mobile broadband connection, click the <span class="guibutton"><strong>Apply</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Point-to-point</strong></span> settings for the connection, click the <span class="guilabel"><strong>PPP Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_PPP_Point-to-Point_Settings">Section 2.2.10.3, “Configuring PPP (Point-to-Point) Settings”</a>;
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">IPv6</code> settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv6_Settings">Section 2.2.10.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div><div class="section" id="sec-Configuring_the_Mobile_Broadband_Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.8.1. Configuring the Mobile Broadband Tab</h4></div></div></div><div class="para">
+ If you have already added a new mobile broadband connection using the assistant (see <a class="xref" href="sec-Establishing_a_Mobile_Broadband_Connection.html#procedure-Adding_a_New_Mobile_Broadband_Connection">Procedure 2.5, “Adding a New Mobile Broadband Connection”</a> for instructions), you can edit the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab to disable roaming if home network is not available, assign a network ID, or instruct <span class="application"><strong>NetworkManager</strong></span> to prefer a certain technology (such as 3G or 2G) when using the connection.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Number</strong></span> </span></dt><dd><div class="para">
+ The number that is dialed to establish a PPP connection with the GSM-based mobile broadband network. This field may be automatically populated during the initial installation of the broadband device. You can usually leave this field blank and enter the <span class="guilabel"><strong>APN</strong></span> instead.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the user name used to authenticate with the network. Some providers do not provide a user name, or accept any user name when connecting to the network.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password used to authenticate with the network. Some providers do not provide a password, or accept any password.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>APN</strong></span> </span></dt><dd><div class="para">
+ Enter the <em class="firstterm">Access Point Name</em> (<acronym class="acronym">APN</acronym>) used to establish a connection with the GSM-based network. Entering the correct APN for a connection is important because it often determines:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ how the user is billed for their network usage; and/or
+ </div></li><li class="listitem"><div class="para">
+ whether the user has access to the Internet, an intranet, or a subnetwork.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Network ID</strong></span> </span></dt><dd><div class="para">
+ Entering a <span class="guilabel"><strong>Network ID</strong></span> causes <span class="application"><strong>NetworkManager</strong></span> to force the device to register only to a specific network. This can be used to ensure the connection does not roam when it is not possible to control roaming directly.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Type</strong></span> </span></dt><dd><div class="para">
+ <span class="guilabel"><strong>Any</strong></span> — The default value of <span class="guilabel"><strong>Any</strong></span> leaves the modem to select the fastest network.
+ </div><div class="para">
+ <span class="guilabel"><strong>3G (UMTS/HSPA)</strong></span> — Force the connection to use only 3G network technologies.
+ </div><div class="para">
+ <span class="guilabel"><strong>2G (GPRS/EDGE)</strong></span> — Force the connection to use only 2G network technologies.
+ </div><div class="para">
+ <span class="guilabel"><strong>Prefer 3G (UMTS/HSPA)</strong></span> — First attempt to connect using a 3G technology such as HSPA or UMTS, and fall back to GPRS or EDGE only upon failure.
+ </div><div class="para">
+ <span class="guilabel"><strong>Prefer 2G (GPRS/EDGE)</strong></span> — First attempt to connect using a 2G technology such as GPRS or EDGE, and fall back to HSPA or UMTS only upon failure.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Allow roaming if home network is not available</strong></span> </span></dt><dd><div class="para">
+ Uncheck this box if you want <span class="application"><strong>NetworkManager</strong></span> to terminate the connection rather than transition from the home network to a roaming one, thereby avoiding possible roaming charges. If the box is checked, <span class="application"><strong>NetworkManager</strong></span> will attempt to maintain a good connection by transitioning from the home network to a roaming one, and vice versa.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>PIN</strong></span> </span></dt><dd><div class="para">
+ If your device's <em class="firstterm">SIM</em> (<em class="firstterm">Subscriber Identity Module</em>) is locked with a <em class="firstterm">PIN</em> (<em class="firstterm">Personal Identification Number</em>), enter the PIN so that <span class="application"><strong>NetworkManager</strong></span> can unlock the device. <span class="application"><strong>NetworkManager</strong></span> must unlock the SIM if a PIN is required in order to use the device for any purpose.
+ </div></dd></dl></div><div class="para">
+ CDMA and EVDO have fewer options. They do not have the <code class="option">APN</code>, <code class="option">Network ID</code>, or <code class="option">Type</code> options.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_a_VPN_Connection.html"><strong>Prev</strong>2.2.7. Establishing a VPN Connection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_a_DSL_Connection.html"><strong>Next</strong>2.2.9. Establishing a DSL Connection</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Establishing_a_VPN_Connection.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Establishing_a_VPN_Connection.html
new file mode 100644
index 0000000..9f743f0
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Establishing_a_VPN_Connection.html
@@ -0,0 +1,81 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.7. Establishing a VPN Connection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html" title="2.2. Using NetworkManager with the GNOME Graphical User Interface" /><link rel="prev" href="sec-Configuring_a_Wi-Fi_Connection.html" title="2.2.6. Configuring a Wi-Fi Connection" /><link rel="next" href="sec-Establishing_a_Mobile_Broadband_Connection.html" title="2.2.8. Establishing a Mobile Broadband Connection" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Sit
e" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_a_Wi-Fi_Connection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_a_Mobile_Broadband_Connection.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Establishing_a_VPN_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.7. Establishing a VPN Connection</h3></div></div></div><div class="para">
+ Establishing a Virtual Private Network (VPN) enables communication between your Local Area Network (LAN), and another, remote LAN. This is done by setting up a tunnel across an intermediate network such as the Internet. The VPN tunnel that is set up typically uses authentication and encryption. After successfully establishing a VPN connection using a secure tunnel, a VPN router or gateway performs the following actions upon the packets you transmit:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ it adds an <em class="firstterm">Authentication Header</em> for routing and authentication purposes;
+ </div></li><li class="listitem"><div class="para">
+ it encrypts the packet data; and,
+ </div></li><li class="listitem"><div class="para">
+ it encloses the data in packets according to the Encapsulating Security Payload (ESP) protocol, which constitutes the decryption and handling instructions.
+ </div></li></ol></div><div class="para">
+ The receiving VPN router strips the header information, decrypts the data, and routes it to its intended destination (either a workstation or other node on a network). Using a network-to-network connection, the receiving node on the local network receives the packets already decrypted and ready for processing. The encryption and decryption process in a network-to-network VPN connection is therefore transparent to clients.
+ </div><div class="para">
+ Because they employ several layers of authentication and encryption, VPNs are a secure and effective means of connecting multiple remote nodes to act as a unified intranet.
+ </div><div class="procedure" id="procedure-Adding_a_New_VPN_Connection"><h6>Procedure 2.3. Adding a New VPN Connection</h6><div class="para">
+ You can configure a new VPN connection by opening the <span class="guilabel"><strong>Network</strong></span> window and selecting the plus symbol below the menu.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the plus symbol below the menu. The <span class="guilabel"><strong>Add Network Connection</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>VPN</strong></span> menu entry. The view now changes to offer configuring a VPN manually, or importing a VPN configuration file.
+ </div><div class="para">
+ The appropriate <span class="application"><strong>NetworkManager</strong></span> VPN plug-in for the VPN type you want to configure must be installed. (see <em class="citetitle">Fedora 20 System Administrator's Guide</em> for more information on how to install new packages in Fedora 20).
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guibutton"><strong>Add</strong></span> button to open the <span class="guilabel"><strong>Choose a VPN Connection Type</strong></span> assistant.
+ </div></li><li class="step"><div class="para">
+ Select the VPN protocol for the gateway you are connecting to from the menu. The VPN protocols available for selection in the menu correspond to the <span class="application"><strong>NetworkManager</strong></span> VPN plug-ins installed. For example, if the <span class="package">NetworkManager-openswan-gnome</span> package is installed then the IPsec based VPN will be selectable from the menu.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Add Network Connection</strong></span> window changes to present the settings customized for the type of VPN connection you selected in the previous step.
+ </div></li></ol></div><div class="procedure" id="procedure-Editing_an_Existing_VPN_Connection"><h6>Procedure 2.4. Editing an Existing VPN Connection</h6><div class="para">
+ You can configure an existing VPN connection by opening the <span class="guilabel"><strong>Network</strong></span> window and selecting the name of the connection from the list. Then click the <span class="guibutton"><strong>Edit</strong></span> button.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>VPN</strong></span> connection you want to edit from the left hand menu.
+ </div></li><li class="step"><div class="para">
+ Click the <span class="guilabel"><strong>Configure</strong></span> button.
+ </div></li></ol></div><h4 id="bh-Configuring_the_Connection_Name_Auto-Connect_Behavior_and_Availability_Settings-vpn">Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Five settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types, see the <span class="guilabel"><strong>General</strong></span> tab:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — Enter a descriptive name for your network connection. This name will be used to list this connection in the menu of the <span class="guilabel"><strong>Network</strong></span> window.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to this network when it is available</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to this connection when it is available. See <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html">Section 2.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>All users may connect to this network</strong></span> — Select this box to create a connection available to all users on the system. Changing this setting may require root privileges. See <a class="xref" href="sec-System-wide_and_Private_Connection_Profiles.html">Section 2.2.4, “System-wide and Private Connection Profiles”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Automatically connect to VPN when using this connection</strong></span> — Select this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to a VPN connection when it is available. Select the VPN from the drop-down menu.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Firewall Zone</strong></span> — Select the Firewall Zone from the dropdown menu.
+ </div></li></ul></div><h4 id="bh-Configuring_the_VPN_Tab">Configuring the VPN Tab</h4><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Gateway</strong></span> </span></dt><dd><div class="para">
+ The name or <code class="systemitem">IP</code> address of the remote VPN gateway.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Group name</strong></span> </span></dt><dd><div class="para">
+ The name of a VPN group configured on the remote gateway.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>User password</strong></span> </span></dt><dd><div class="para">
+ If required, enter the password used to authenticate with the VPN.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Group password</strong></span> </span></dt><dd><div class="para">
+ If required, enter the password used to authenticate with the VPN.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>User name</strong></span> </span></dt><dd><div class="para">
+ If required, enter the user name used to authenticate with the VPN.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Phase1 Algorithms</strong></span> </span></dt><dd><div class="para">
+ If required, enter the algorithms to be used to authenticate and set up an encrypted channel.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Phase2 Algorithms</strong></span> </span></dt><dd><div class="para">
+ If required, enter the algorithms to be used for the IPsec negotiations.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guilabel"><strong>Domain</strong></span> </span></dt><dd><div class="para">
+ If required, enter the Domain Name.
+ </div></dd></dl></div><h4 id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-vpn">Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your new VPN connection, click the <span class="guibutton"><strong>Save</strong></span> button to save your customized configuration. If the profile was in use while being edited, power cycle the connection to make <span class="application"><strong>NetworkManager</strong></span> apply the changes. If the profile is OFF, set it to ON. See <a class="xref" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html#sec-Connecting_to_a_Network_Using_a_GUI">Section 2.2.1, “Connecting to a Network Using a GUI”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ You can further configure an existing connection by selecting it in the <span class="guilabel"><strong>Network</strong></span> window and clicking <span class="guilabel"><strong>Configure</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">IPv4</code> settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_IPv4_Settings">Section 2.2.10.4, “Configuring IPv4 Settings”</a>.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_a_Wi-Fi_Connection.html"><strong>Prev</strong>2.2.6. Configuring a Wi-Fi Connection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_a_Mobile_Broadband_Connection.html"><strong>Next</strong>2.2.8. Establishing a Mobile Broadband Connection</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Install_the_Network_Teaming_Daemon.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Install_the_Network_Teaming_Daemon.html
new file mode 100644
index 0000000..b448566
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Install_the_Network_Teaming_Daemon.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.5. Install the Network Teaming Daemon</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Teaming.html" title="Chapter 5. Configure Network Teaming" /><link rel="prev" href="sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners.html" title="5.4. Understanding the Network Teaming Daemon and the "Runners"" /><link rel="next" href="sec-Converting_a_Bond_to_a_Team.html" title="5.6. Converting a Bond to a Team" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><l
i class="previous"><a accesskey="p" href="sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Converting_a_Bond_to_a_Team.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Install_the_Network_Teaming_Daemon"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.5. Install the Network Teaming Daemon</h2></div></div></div><div class="para">
+ The networking teaming daemon, <code class="systemitem">teamd</code>, is not installed by default. To install <code class="systemitem">teamd</code>, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">yum install teamd</code></pre>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners.html"><strong>Prev</strong>5.4. Understanding the Network Teaming Daemon and...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Converting_a_Bond_to_a_Team.html"><strong>Next</strong>5.6. Converting a Bond to a Team</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Installing_NetworkManager.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Installing_NetworkManager.html
new file mode 100644
index 0000000..175aeb7
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Installing_NetworkManager.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3. Installing NetworkManager</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Introduction_to_Fedora_Networking.html" title="Chapter 1. Introduction to Fedora Networking" /><link rel="prev" href="sec-Introduction_to_NetworkManager.html" title="1.2. Introduction to NetworkManager" /><link rel="next" href="sec-Interacting_with_NetworkManager.html" title="1.3.2. Interacting with NetworkManager" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" hr
ef="sec-Introduction_to_NetworkManager.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Interacting_with_NetworkManager.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Installing_NetworkManager"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.3. Installing NetworkManager</h2></div></div></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> is installed by default on Fedora. If necessary, to ensure that it is, run the following command as the <code class="systemitem">root</code> user:
+ </div><pre class="screen">~]# <code class="command">yum install NetworkManager</code></pre><div class="para">
+ For information on user privileges and gaining privileges, see the <em class="citetitle">Fedora 20 System Administrator's Guide</em>.
+ </div><div class="section" id="sec-The_NetworkManager_Daemon"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.3.1. The NetworkManager Daemon</h3></div></div></div><div class="para">
+ The <span class="application"><strong>NetworkManager</strong></span> daemon runs with root privileges and is, by default, configured to start up at boot time. You can determine whether the <span class="application"><strong>NetworkManager</strong></span> daemon is running by entering this command:
+ </div><pre class="screen">~]$ <code class="command">systemctl status NetworkManager</code>
+NetworkManager.service - Network Manager
+ Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled)
+ Active: active (running) since Fri, 08 Mar 2013 12:50:04 +0100; 3 days ago</pre><div class="para">
+ The <code class="command">systemctl status</code> command will report <span class="application"><strong>NetworkManager</strong></span> as <code class="computeroutput">Active: inactive (dead)</code> if the <span class="application"><strong>NetworkManager</strong></span> service is not running. To start it for the current session run the following command as the root user:
+ </div><pre class="screen">~]# <code class="command">systemctl start NetworkManager</code></pre><div class="para">
+ Run the <code class="command">systemctl enable</code> command to ensure that <span class="application"><strong>NetworkManager</strong></span> starts up every time the system boots:
+ </div><pre class="screen">~]# <code class="command">systemctl enable NetworkManager</code></pre><div class="para">
+ For more information on starting, stopping and managing services, see the <em class="citetitle">Fedora 20 System Administrator's Guide</em>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Introduction_to_NetworkManager.html"><strong>Prev</strong>1.2. Introduction to NetworkManager</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Interacting_with_NetworkManager.html"><strong>Next</strong>1.3.2. Interacting with NetworkManager</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Interacting_with_NetworkManager.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Interacting_with_NetworkManager.html
new file mode 100644
index 0000000..dec7f92
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Interacting_with_NetworkManager.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.2. Interacting with NetworkManager</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Installing_NetworkManager.html" title="1.3. Installing NetworkManager" /><link rel="prev" href="sec-Installing_NetworkManager.html" title="1.3. Installing NetworkManager" /><link rel="next" href="sec-Network_Config_Using_CLI.html" title="1.4. Network Configuration Using the Command Line Interface (CLI)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Inst
alling_NetworkManager.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Config_Using_CLI.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Interacting_with_NetworkManager"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.3.2. Interacting with NetworkManager</h3></div></div></div><div class="para">
+ Users do not interact with the <span class="application"><strong>NetworkManager</strong></span> system service directly. Instead, users perform network configuration tasks via graphical and command-line user interface tools. The following tools are available in Fedora:
+ </div><div class="para">
+ <div class="orderedlist"><ol><li class="listitem"><div class="para">
+ A graphical user interface tool called <span class="application"><strong>control-center</strong></span>, provided by GNOME, is available for desktop users. It incorporates a <span class="application"><strong>Network</strong></span> settings tool. It start it, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ A command-line tool, <span class="application"><strong>nmcli</strong></span>, is provided to allow users and scripts to interact with <span class="application"><strong>NetworkManager</strong></span>. Note that <span class="application"><strong>nmcli</strong></span> can be used on GUI-less systems like servers to control all aspects of <span class="application"><strong>NetworkManager</strong></span>. It is on an equal footing with the GUI tools.
+ </div></li><li class="listitem"><div class="para">
+ The GNOME Shell also provides a network icon in its Notification Area representing network connection states as reported by <span class="application"><strong>NetworkManager</strong></span>. The icon has multiple states that serve as visual indicators for the type of connection you are currently using.
+ </div></li><li class="listitem"><div class="para">
+ A graphical user interface tool called <span class="application"><strong>control-center</strong></span>, provided by the GNOME Shell, is available for desktop users. It incorporates a <span class="application"><strong>Network</strong></span> settings tool. To start it, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="keycap"><strong>Super</strong></span> key appears in a variety of guises, depending on the keyboard and other hardware, but often as either the Windows or Command key, and typically to the left of the Spacebar.
+ </div></li><li class="listitem"><div class="para">
+ A graphical user interface tool, <span class="application"><strong>nm-connection-editor</strong></span>, is available for certain tasks not yet handled by <span class="application"><strong>control-center</strong></span>. To start it, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">network connections</code> or <code class="command">nm-connection-editor</code> and then press <span class="keycap"><strong>Enter</strong></span>.
+ </div></li></ol></div>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing_NetworkManager.html"><strong>Prev</strong>1.3. Installing NetworkManager</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Config_Using_CLI.html"><strong>Next</strong>1.4. Network Configuration Using the Command Line...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Introduction_to_Fedora_Networking-additional_resources.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Introduction_to_Fedora_Networking-additional_resources.html
new file mode 100644
index 0000000..b943b0f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Introduction_to_Fedora_Networking-additional_resources.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.8. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Introduction_to_Fedora_Networking.html" title="Chapter 1. Introduction to Fedora Networking" /><link rel="prev" href="sec-Network_Configuration_Using_sysconfig_Files.html" title="1.7. Network Configuration Using sysconfig Files" /><link rel="next" href="ch-Configure_Networking.html" title="Chapter 2. Configure Networking" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesske
y="p" href="sec-Network_Configuration_Using_sysconfig_Files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Configure_Networking.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Introduction_to_Fedora_Networking-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.8. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding networking for Fedora.
+ </div><div class="section" id="sec-Introduction_to_Fedora_Networking-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.8.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">man(1)</code> man page — Describes man pages and how to find them.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">NetworkManager(8)</code> man page — Describes the network management daemon.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">NetworkManager.conf(5)</code> man page — Describes the <code class="systemitem">NetworkManager</code> configuration file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code>version</code></em>/sysconfig.txt</code> — Describes configuration files and their directives.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Network_Configuration_Using_sysconfig_Files.html"><strong>Prev</strong>1.7. Network Configuration Using sysconfig Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Configure_Networking.html"><strong>Next</strong>Chapter 2. Configure Networking</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Introduction_to_NetworkManager.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Introduction_to_NetworkManager.html
new file mode 100644
index 0000000..54de0c6
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Introduction_to_NetworkManager.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2. Introduction to NetworkManager</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Introduction_to_Fedora_Networking.html" title="Chapter 1. Introduction to Fedora Networking" /><link rel="prev" href="ch-Introduction_to_Fedora_Networking.html" title="Chapter 1. Introduction to Fedora Networking" /><link rel="next" href="sec-Installing_NetworkManager.html" title="1.3. Installing NetworkManager" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href
="ch-Introduction_to_Fedora_Networking.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Installing_NetworkManager.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Introduction_to_NetworkManager"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.2. Introduction to NetworkManager</h2></div></div></div><div class="para">
+ As of Fedora 20, the default networking service is provided by <code class="systemitem">NetworkManager</code>, which is a dynamic network control and configuration daemon that attempts to keep network devices and connections up and active when they are available. The traditional <code class="filename">ifcfg</code> type configuration files are still supported. See <a class="xref" href="sec-NetworkManager_and_the_Network_Scripts.html">Section 1.6, “NetworkManager and the Network Scripts”</a> for more information.
+ </div><div class="table" id="tb-A_Summary_of_Networking_Tools_and_Applications"><h6>Table 1.1. A Summary of Networking Tools and Applications</h6><div class="table-contents"><table summary="A Summary of Networking Tools and Applications" border="1"><colgroup><col width="29%" align="left" class="c1" /><col width="71%" align="left" class="c2" /></colgroup><thead><tr><th class="" align="left">
+ Application or Tool
+ </th><th class="" align="left">
+ Description
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ <span class="application"><strong>NetworkManager</strong></span>
+ </td><td class="" align="left">
+ The default networking daemon
+ </td></tr><tr><td class="" align="left">
+ <span class="application"><strong>nmtui</strong></span>
+ </td><td class="" align="left">
+ A simple curses-based text user interface (TUI) for <span class="application"><strong>NetworkManager</strong></span>
+ </td></tr><tr><td class="" align="left">
+ <span class="application"><strong>nmcli</strong></span>
+ </td><td class="" align="left">
+ A command-line tool provided to allow users and scripts to interact with <span class="application"><strong>NetworkManager</strong></span>
+ </td></tr><tr><td class="" align="left">
+ <span class="application"><strong>control-center</strong></span>
+ </td><td class="" align="left">
+ A graphical user interface tool provided by the GNOME Shell
+ </td></tr><tr><td class="" align="left">
+ <span class="application"><strong>nm-connection-editor</strong></span>
+ </td><td class="" align="left">
+ A GTK+ 3 application available for certain tasks not yet handled by <span class="application"><strong>control-center</strong></span>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ <code class="systemitem">NetworkManager</code> can be used with the following types of connections: Ethernet, VLANs, Bridges, Bonds, Teams, Wi-Fi, mobile broadband (such as cellular 3G), and IP-over-InfiniBand. For these connection types, <code class="systemitem">NetworkManager</code> can configure network aliases, <code class="systemitem">IP</code> addresses, static routes, <code class="systemitem">DNS</code> information, and VPN connections, as well as many connection-specific parameters. Finally, <code class="systemitem">NetworkManager</code> provides an API via D-Bus which allows applications to query and control network configuration and state.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Introduction_to_Fedora_Networking.html"><strong>Prev</strong>Chapter 1. Introduction to Fedora Networking</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Installing_NetworkManager.html"><strong>Next</strong>1.3. Installing NetworkManager</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Listing_the_ports_of_a_Team_Using_teamnl.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Listing_the_ports_of_a_Team_Using_teamnl.html
new file mode 100644
index 0000000..2fe25a7
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Listing_the_ports_of_a_Team_Using_teamnl.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.4. Listing the ports of a Team Using teamnl</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_a_Network_Team_Using-the_Command_Line.html" title="5.10. Configure a Network Team Using the Command Line" /><link rel="prev" href="sec-Add_a_port_to_a_Network_Team_Using_iputils.html" title="5.10.3. Add a Port to a Network Team Using iputils" /><link rel="next" href="sec-Configuring_Options_of_a_Team_Using_teamnl.html" title="5.10.5. Configuring Options of a Team Using teamnl" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Si
te" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Add_a_port_to_a_Network_Team_Using_iputils.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Options_of_a_Team_Using_teamnl.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Listing_the_ports_of_a_Team_Using_teamnl"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.4. Listing the ports of a Team Using teamnl</h3></div></div></div><div class="para">
+ To view or list the ports in a network team, using the <span class="application"><strong>teamnl</strong></span> utility, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamnl team0 ports</code>
+em2: up 100 fullduplex
+em1: up 100 fullduplex</pre>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Add_a_port_to_a_Network_Team_Using_iputils.html"><strong>Prev</strong>5.10.3. Add a Port to a Network Team Using iputils</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Options_of_a_Team_Using_teamnl.html"><strong>Next</strong>5.10.5. Configuring Options of a Team Using teamnl</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Naming_Scheme_for_Network_Devices_Available_for_Linux_on_System_z.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Naming_Scheme_for_Network_Devices_Available_for_Linux_on_System_z.html
new file mode 100644
index 0000000..318f834
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Naming_Scheme_for_Network_Devices_Available_for_Linux_on_System_z.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.4. Naming Scheme for Network Devices Available for Linux on System z</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Consistent_Network_Device_Naming.html" title="Chapter 8. Consistent Network Device Naming" /><link rel="prev" href="sec-Understanding_the_Predictable_Network_Interface_Device_Names.html" title="8.3. Understanding the Predictable Network Interface Device Names" /><link rel="next" href="sec-Naming_Scheme_for_VLAN_Interfaces.html" title="8.5. Naming Scheme for VLAN Interfaces" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p
><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Understanding_the_Predictable_Network_Interface_Device_Names.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Naming_Scheme_for_VLAN_Interfaces.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Naming_Scheme_for_Network_Devices_Available_for_Linux_on_System_z"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.4. Naming Scheme for Network Devices Available for Linux on System z</h2></div></div></div><div class="para">
+ Use the bus-ID to create predictable device names for network interfaces in Linux on System z instances. The bus-ID identifies a device in the s390 channel subsystem. A bus ID identifies the device within the scope of a Linux instance. For a CCW device, the bus ID is the device's device number with a leading <code class="literal">0.n</code>, where <code class="literal">n</code> is the subchannel set ID. For example, <code class="literal">0.1.0ab1</code>.
+ </div><div class="para">
+ Network interfaces of device type Ethernet are named as follows: <pre class="synopsis">enccw<em class="replaceable"><code>0</code></em>.<em class="replaceable"><code>0</code></em>.<em class="replaceable"><code>1234</code></em></pre>
+ </div><div class="para">
+ CTC network devices of device type SLIP are named as follows: <pre class="synopsis">slccw<em class="replaceable"><code>0</code></em>.<em class="replaceable"><code>0</code></em>.<em class="replaceable"><code>1234</code></em></pre>
+ </div><div class="para">
+ Use the <code class="command">znetconf -c</code> command or the <code class="command">lscss -a</code> command to display available network devices and their bus-IDs.
+ </div><div class="table" id="Device_Name_Types_for_Linux_on_System_z"><h6>Table 8.2. Device Name Types for Linux on System z</h6><div class="table-contents"><table summary="Device Name Types for Linux on System z" border="1"><colgroup><col width="63%" class="Format" /><col width="38%" class="Description" /></colgroup><thead><tr><th class="">
+ Format
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ enccw<em class="replaceable"><code>bus-ID</code></em>
+ </td><td class="">
+ device type Ethernet
+ </td></tr><tr><td class="">
+ slccw<em class="replaceable"><code>bus-ID</code></em>
+ </td><td class="">
+ CTC network devices of device type SLIP
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Understanding_the_Predictable_Network_Interface_Device_Names.html"><strong>Prev</strong>8.3. Understanding the Predictable Network Interf...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Naming_Scheme_for_VLAN_Interfaces.html"><strong>Next</strong>8.5. Naming Scheme for VLAN Interfaces</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Naming_Scheme_for_VLAN_Interfaces.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Naming_Scheme_for_VLAN_Interfaces.html
new file mode 100644
index 0000000..db4d033
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Naming_Scheme_for_VLAN_Interfaces.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.5. Naming Scheme for VLAN Interfaces</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Consistent_Network_Device_Naming.html" title="Chapter 8. Consistent Network Device Naming" /><link rel="prev" href="sec-Naming_Scheme_for_Network_Devices_Available_for_Linux_on_System_z.html" title="8.4. Naming Scheme for Network Devices Available for Linux on System z" /><link rel="next" href="sec-Consistent_Network_Device_Naming_Using_biosdevname.html" title="8.6. Consistent Network Device Naming Using biosdevname" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_r
ight.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Naming_Scheme_for_Network_Devices_Available_for_Linux_on_System_z.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Consistent_Network_Device_Naming_Using_biosdevname.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Naming_Scheme_for_VLAN_Interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.5. Naming Scheme for VLAN Interfaces</h2></div></div></div><div class="para">
+ Traditionally, VLAN interface names in the format: <em class="replaceable"><code>interface-name</code></em>.<em class="replaceable"><code>VLAN-ID</code></em> are used. The <code class="literal">VLAN-ID</code> ranges from <code class="literal">0</code> to <code class="literal">4096</code>, which is a maximum of four characters and the total interface name has a limit of 15 characters. The maximum interface name length is defined by the kernel headers and is a global limit, affecting all applications.
+ </div><div class="para">
+ In Fedora, four naming conventions for VLAN interface names are supported:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">VLAN plus VLAN ID </span></dt><dd><div class="para">
+ The word <code class="literal">vlan</code> plus the VLAN ID. For example: vlan0005
+ </div></dd><dt class="varlistentry"><span class="term">VLAN plus VLAN ID without padding</span></dt><dd><div class="para">
+ The word <code class="literal">vlan</code> plus the VLAN ID with out padding by means of an additional two zeros. For example: vlan5
+ </div></dd><dt class="varlistentry"><span class="term">Device name plus VLAN ID</span></dt><dd><div class="para">
+ The name of the parent interface plus the VLAN ID. For example: eth0.0005
+ </div></dd><dt class="varlistentry"><span class="term">Device name plus VLAN ID without padding</span></dt><dd><div class="para">
+ The name of the parent interface plus the VLAN ID with out padding by means of an additional two zeros. For example: eth0.05
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Naming_Scheme_for_Network_Devices_Available_for_Linux_on_System_z.html"><strong>Prev</strong>8.4. Naming Scheme for Network Devices Available ...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Consistent_Network_Device_Naming_Using_biosdevname.html"><strong>Next</strong>8.6. Consistent Network Device Naming Using biosd...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-NetworkManager_and_the_Network_Scripts.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-NetworkManager_and_the_Network_Scripts.html
new file mode 100644
index 0000000..f85f0c8
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-NetworkManager_and_the_Network_Scripts.html
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.6. NetworkManager and the Network Scripts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Introduction_to_Fedora_Networking.html" title="Chapter 1. Introduction to Fedora Networking" /><link rel="prev" href="sec-Network_Config_Using_nmcli.html" title="1.5. Network Configuration Using NetworkManager's CLI (nmcli)" /><link rel="next" href="sec-Network_Configuration_Using_sysconfig_Files.html" title="1.7. Network Configuration Using sysconfig Files" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docn
av"><li class="previous"><a accesskey="p" href="sec-Network_Config_Using_nmcli.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Configuration_Using_sysconfig_Files.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-NetworkManager_and_the_Network_Scripts"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.6. NetworkManager and the Network Scripts</h2></div></div></div><div class="para">
+ In previous Red Hat Enterprise Linux releases, the default way to configure networking was using <em class="firstterm">network scripts</em>. The term <em class="firstterm">network scripts</em> is commonly used for the script <code class="filename">/etc/init.d/network</code> and any other installed scripts it calls. The user supplied files are typically viewed as configuration, but can also be interpreted as an amendment to the scripts.
+ </div><div class="para">
+ Although <span class="application"><strong>NetworkManager</strong></span> provides the default networking service, Red Hat developers have worked hard to ensure that scripts and <span class="application"><strong>NetworkManager</strong></span> cooperate with each other. Administrators who are used to the scripts can certainly continue to use them. We expect both systems to be able to run in parallel and work well together. It is expected that most user shell scripts from previous releases will still work. Red Hat recommends that you test them first.
+ </div><h3 id="bh-Running_Network_Script">Running Network Script</h3><div class="para">
+ Run the script <span class="bold bold"><strong>only</strong></span> with the <span class="application"><strong>systemctl</strong></span> utility which will clear any existing environment variables and ensure clean execution. The command takes the following form: <pre class="synopsis"><code class="command">systemctl <code class="option">start|stop|restart|status</code> network</code></pre>
+ </div><div class="para">
+ <span class="bold bold"><strong>Do not run</strong></span> any service by calling <code class="command">/etc/init.d/<em class="replaceable"><code>servicename</code></em> <code class="option">start|stop|restart|status</code></code> directly.
+ </div><div class="para">
+ Note that in Red Hat Enterprise Linux 7, <span class="application"><strong>NetworkManager</strong></span> is started first, and <code class="filename">/etc/init.d/network</code> checks with <span class="application"><strong>NetworkManager</strong></span> to avoid tampering with <span class="application"><strong>NetworkManager</strong></span>'s connections. <span class="application"><strong>NetworkManager</strong></span> is intended to be the primary application using sysconfig configuration files and <code class="filename">/etc/init.d/network</code> is intended to be secondary, playing a fallback role.
+ </div><div class="para">
+ The <code class="filename">/etc/init.d/network</code> script is not event-driven, it runs either:
+ <div class="orderedlist"><ol><li class="listitem"><div class="para">
+ manually (by one of the <code class="command">systemctl</code> commands <code class="command"><code class="option">start|stop|restart</code> network</code>),
+ </div></li><li class="listitem"><div class="para">
+ on boot and shutdown if the network service is enabled (as a result of the command <code class="command">systemctl enable network</code>).
+ </div></li></ol></div>
+ It is a manual process and does not react to events that happen after boot. Users can also call the scripts <code class="filename">ifup</code> and <code class="filename">ifdown</code> manually.
+ </div><div class="para">
+
+ </div><h3 id="bh-Custom_Commands_and_the_Network_Scripts">Custom Commands and the Network Scripts</h3><div class="para">
+ Custom commands in the scripts <code class="filename">/sbin/ifup-local</code>, <code class="filename">ifdown-pre-local</code>, and <code class="filename">ifdown-local</code> are only executed when those devices are controlled by the <code class="systemitem">/etc/init.d/network</code> service. If you modified the initscripts themselves (for example, <code class="filename">/etc/sysconfig/network-scripts/ifup-eth</code>) then those changes would be overwritten by an <span class="package">initscripts</span> package update. Therefore it is recommend that you avoid modifying the initscripts directly and make use of the <code class="filename">/sbin/if*local</code> scripts, so that your custom changes will survive package updates. The initscripts just check for the presence of the relevant <code class="filename">/sbin/if*local</code> and run them if they exit. The initscripts do not place anything in the <code class="filename">/sbin/if*local</code> scripts, nor does the <span cla
ss="package">initscripts</span> RPM (or any package) own or modify those files.
+ </div><div class="para">
+ There are ways to perform custom tasks when network connections go up and down, both with the old network scripts and with <span class="application"><strong>NetworkManager</strong></span>. When <span class="application"><strong>NetworkManager</strong></span> is enabled, the <code class="filename">ifup</code> and <code class="filename">ifdown</code> script will ask <span class="application"><strong>NetworkManager</strong></span> whether <span class="application"><strong>NetworkManager</strong></span> manages the interface in question, which is found from the <span class="quote">“<span class="quote">DEVICE=</span>”</span> line in the <code class="filename">ifcfg</code> file. If <span class="application"><strong>NetworkManager</strong></span> does manage that device, and the device is not already connected, then <code class="filename">ifup</code> will ask <span class="application"><strong>NetworkManager</strong></span> to start the connection.
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If the device is managed by <span class="application"><strong>NetworkManager</strong></span> and it <span class="bold bold"><strong>is</strong></span> already connected, nothing is done.
+ </div></li><li class="listitem"><div class="para">
+ If the device is not managed by <span class="application"><strong>NetworkManager</strong></span>, then the scripts will start the connection using the older, non-<span class="application"><strong>NetworkManager</strong></span> mechanisms that they have used since the time before <span class="application"><strong>NetworkManager</strong></span> existed.
+ </div></li></ul></div>
+ </div><div class="para">
+ If you are calling "<code class="filename">ifdown</code>" and the device is managed by <span class="application"><strong>NetworkManager</strong></span>, then <code class="filename">ifdown</code> will ask <span class="application"><strong>NetworkManager</strong></span> to terminate the connection.
+ </div><div class="para">
+ The scripts dynamically check <span class="application"><strong>NetworkManager</strong></span>, so if <span class="application"><strong>NetworkManager</strong></span> is not running, the scripts will fall back to the old, pre-<span class="application"><strong>NetworkManager</strong></span> script-based mechanisms.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Network_Config_Using_nmcli.html"><strong>Prev</strong>1.5. Network Configuration Using NetworkManager's...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Configuration_Using_sysconfig_Files.html"><strong>Next</strong>1.7. Network Configuration Using sysconfig Files</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Bonding_Using_the_Command_Line_Interface.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Bonding_Using_the_Command_Line_Interface.html
new file mode 100644
index 0000000..d62a5f7
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Bonding_Using_the_Command_Line_Interface.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.3. Using the Command Line Interface (CLI)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Bonding.html" title="Chapter 4. Configure Network Bonding" /><link rel="prev" href="sec-Creating_a_Bond_Connection_Using_a_GUI.html" title="4.2. Creating a Bond Connection Using a GUI" /><link rel="next" href="sec-Create_a_Channel_Bonding_Interface.html" title="4.3.2. Create a Channel Bonding Interface" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey=
"p" href="sec-Creating_a_Bond_Connection_Using_a_GUI.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Create_a_Channel_Bonding_Interface.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Network_Bonding_Using_the_Command_Line_Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. Using the Command Line Interface (CLI)</h2></div></div></div><div class="para">
+ A bond is created using the <code class="filename">bonding</code> kernel module and a special network interface called a <em class="firstterm">channel bonding interface</em>.
+ </div><div class="section" id="sec-Check_if_Bonding_Kernel_Module_is_Installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.1. Check if Bonding Kernel Module is Installed</h3></div></div></div><div class="para">
+ In Fedora, the bonding module is not loaded by default. You can load the module by issuing the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">modprobe --first-time bonding</code></pre>
+ This activation will not persist across system restarts. See the <em class="citetitle">Fedora 20 System Administrator's Guide</em> for an explanation of persistent module loading. Note that given a correct configuration file using the <code class="command">BONDING_OPTS</code> directive, the bonding module will be loaded as required and therefore does not need to be loaded separately.
+ </div><div class="para">
+ To display information about the module, issue the following command:
+<pre class="screen">~]$ <code class="command">modinfo bonding</code></pre>
+ See the <code class="filename">modprobe(8)</code> man page for more command options.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Creating_a_Bond_Connection_Using_a_GUI.html"><strong>Prev</strong>4.2. Creating a Bond Connection Using a GUI</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Create_a_Channel_Bonding_Interface.html"><strong>Next</strong>4.3.2. Create a Channel Bonding Interface</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli.html
new file mode 100644
index 0000000..e9ce882
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.5. Using the NetworkManager Command Line Tool, nmcli</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Bonding.html" title="Chapter 4. Configure Network Bonding" /><link rel="prev" href="sec-Using_Channel_Bonding.html" title="4.4. Using Channel Bonding" /><link rel="next" href="sec-Configure_Network_Bonding-additional_resources.html" title="4.6. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_Channel_Bonding.ht
ml"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_Network_Bonding-additional_resources.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.5. Using the NetworkManager Command Line Tool, nmcli</h2></div></div></div><div class="para">
+ To create a bond, named <em class="replaceable"><code>mybond0</code></em>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type bond con-name <em class="replaceable"><code>mybond0</code></em> ifname <em class="replaceable"><code>mybond0</code></em> mode active-backup</code>
+Connection 'mybond0' (9301ff97-abbc-4432-aad1-246d7faea7fb) successfully added.</pre>
+ To add a slave interface, issue a command in the following form:
+<pre class="screen">~]$ <code class="command">nmcli con add type bond-slave ifname <em class="replaceable"><code>ens7</code></em> master <em class="replaceable"><code>mybond0</code></em></code></pre>
+ To add additional slaves, repeat the previous command with a new interface, for example:
+<pre class="screen">~]$ <code class="command">nmcli con add type bond-slave ifname <em class="replaceable"><code>ens3</code></em> master <em class="replaceable"><code>mybond0</code></em></code>
+Connection 'bond-slave-ens3-1' (50c59350-1531-45f4-ba04-33431c16e386) successfully added.</pre>
+ Note that as no <code class="command">con-name</code> was given for the slaves, the name was derived from the interface name by prepending the type. At time of writing, <span class="application"><strong>nmcli</strong></span> only supports Ethernet slaves.
+ </div><div class="para">
+ In order to bring up a bond, the slaves must be brought up first as follows:
+<pre class="screen">~]$ <code class="command">nmcli con up bond-slave-<em class="replaceable"><code>ens7</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/14)</pre>
+
+<pre class="screen">~]$ <code class="command">nmcli con up bond-slave-<em class="replaceable"><code>ens3</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/15)</pre>
+ Now bring up the bond as follows:
+<pre class="screen">~]$ <code class="command">nmcli con up bond-<em class="replaceable"><code>mybond0</code></em></code>
+Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/16)</pre>
+
+ </div><div class="para">
+ See <a class="xref" href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html">Section 2.4, “Using the NetworkManager Command Line Tool, nmcli”</a> for an introduction to <span class="application"><strong>nmcli</strong></span>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_Channel_Bonding.html"><strong>Prev</strong>4.4. Using Channel Bonding</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_Network_Bonding-additional_resources.html"><strong>Next</strong>4.6. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Bridging-additional_resources.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Bridging-additional_resources.html
new file mode 100644
index 0000000..5a2ab6f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Bridging-additional_resources.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.4. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Bridging.html" title="Chapter 6. Configure Network Bridging" /><link rel="prev" href="sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html" title="6.3. Using the NetworkManager Command Line Tool, nmcli" /><link rel="next" href="ch-Configure_802_1Q_VLAN_Tagging.html" title="Chapter 7. Configure 802.1Q VLAN tagging" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docn
av"><li class="previous"><a accesskey="p" href="sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Configure_802_1Q_VLAN_Tagging.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Network_Bridging-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.4. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding network bridging.
+ </div><div class="section" id="sec-Network_Bridging-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.4.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">nmcli(1)</code> man page — Describes <span class="application"><strong>NetworkManager</strong></span>'s command‐line tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nmcli-examples(5)</code> man page — Gives examples of <span class="application"><strong>nmcli</strong></span> commands.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nm-settings(5)</code> man page — Description of settings and parameters of <span class="application"><strong>NetworkManager</strong></span> connections.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html"><strong>Prev</strong>6.3. Using the NetworkManager Command Line Tool, ...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Configure_802_1Q_VLAN_Tagging.html"><strong>Next</strong>Chapter 7. Configure 802.1Q VLAN tagging</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Bridging_Using_the_Command_Line_Interface.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Bridging_Using_the_Command_Line_Interface.html
new file mode 100644
index 0000000..607b343
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Bridging_Using_the_Command_Line_Interface.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2. Using the Command Line Interface (CLI)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Bridging.html" title="Chapter 6. Configure Network Bridging" /><link rel="prev" href="ch-Configure_Network_Bridging.html" title="Chapter 6. Configure Network Bridging" /><link rel="next" href="sec-Create_a_Network_Bridge.html" title="6.2.2. Create a Network Bridge" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Configure_Network_Bridgin
g.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Create_a_Network_Bridge.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Network_Bridging_Using_the_Command_Line_Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.2. Using the Command Line Interface (CLI)</h2></div></div></div><div class="section" id="sec-Check_if_Bridging_Kernel_Module_is_Installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">6.2.1. Check if Bridging Kernel Module is Installed</h3></div></div></div><div class="para">
+ In Fedora, the bridging module is loaded by default. If necessary, you can make sure that the module is loaded by issuing the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">modprobe --first-time bridge</code>
+modprobe: ERROR: could not insert 'bridge': Module already in kernel</pre>
+ To display information about the module, issue the following command:
+<pre class="screen">~]$ <code class="command">modinfo bridge</code></pre>
+ See the <code class="filename">modprobe(8)</code> man page for more command options.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Configure_Network_Bridging.html"><strong>Prev</strong>Chapter 6. Configure Network Bridging</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Create_a_Network_Bridge.html"><strong>Next</strong>6.2.2. Create a Network Bridge</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html
new file mode 100644
index 0000000..df122e8
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.3. Using the NetworkManager Command Line Tool, nmcli</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Bridging.html" title="Chapter 6. Configure Network Bridging" /><link rel="prev" href="sec-Create_a_Network_Bridge.html" title="6.2.2. Create a Network Bridge" /><link rel="next" href="sec-Network_Bridging-additional_resources.html" title="6.4. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Create_a_Network_Bridge.h
tml"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Bridging-additional_resources.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Network_Bridging_sec-Using_the_NetworkManager_Command_Line_Tool_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.3. Using the NetworkManager Command Line Tool, nmcli</h2></div></div></div><div class="para">
+ To create a bridge, with name <span class="interface">bridge-br0</span>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type bridge ifname br0</code>
+Connection 'bridge-br0' (79cf6a3e-0310-4a78-b759-bda1cc3eef8d) successfully added.</pre>
+ If no interface name is specified, the name will default to <span class="interface">bridge</span>, <span class="interface">bridge-1</span>, <span class="interface">bridge-2</span>, and so on.
+ </div><div class="para">
+ To view the connections, issue the following command:
+<pre class="screen">~]$ <code class="command">nmcli con show conf</code>
+NAME UUID TYPE TIMESTAMP-REAL
+eth0 4d5c449a-a6c5-451c-8206-3c9a4ec88bca 802-3-ethernet Mon 21 Oct 2013 16:01:53 BST
+bridge-br0 79cf6a3e-0310-4a78-b759-bda1cc3eef8d bridge never</pre>
+
+ </div><div class="para">
+ <em class="firstterm">Spanning tree protocol</em> (<acronym class="acronym">STP</acronym>) according to the IEEE 802.1D standard is enabled by default. To disable <code class="systemitem">STP</code> for this bridge, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con bridge-br0 stp no</code></pre>
+ To re-enable <code class="systemitem">802.1D STP</code> for this bridge, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con bridge-br0 stp yes</code></pre>
+
+ </div><div class="para">
+ The default bridge priority for <code class="systemitem">802.1D STP</code> is <code class="literal">32768</code>. The lower number is preferred in root bridge selection. For example, a bridge with priority of <code class="literal">28672</code> would be selected as the root bridge in preference to a bridge with priority value of <code class="literal">32768</code> (the default). To create a bridge with a non-default value, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type bridge ifname br5 stp yes priority 28672</code>
+Connection 'bridge-br5' (86b83ad3-b466-4795-aeb6-4a66eb1856c7) successfully added.</pre>
+ The allowed values are in the range <code class="literal">0</code> to <code class="literal">65535</code>, but can only be set in multiples of <code class="literal">4096</code>.
+ </div><div class="para">
+ To change the bridge priority of an existing bridge to a non-default value, issue a command in the following format:
+<pre class="screen">~]$ <code class="command">nmcli connection modify bridge-br5 bridge.priority 36864</code></pre>
+ The allowed values are in the range <code class="literal">0</code> to <code class="literal">65535</code>, but can only be set in multiples of <code class="literal">4096</code>.
+ </div><div class="para">
+ Further options for <code class="systemitem">802.1D STP</code> are listed in the bridge section of the <code class="filename">nmcli(1)</code> man page.
+ </div><div class="para">
+ To add, or enslave an interface, for example <span class="interface">eth1</span>, to the bridge <span class="interface">bridge-br0</span>, issue a command as follows:
+<pre class="screen">~]$ <code class="command">nmcli con add type bridge-slave ifname eth1 master bridge-br0</code>
+Connection 'bridge-slave-eth1' (70ffae80-7428-4d9c-8cbd-2e35de72476e) successfully added.</pre>
+ At time of writing, <span class="application"><strong>nmcli</strong></span> only supports Ethernet slaves.
+ </div><div class="para">
+ To change a value using interactive mode, issue the following command:
+<pre class="screen">~]$ <code class="command">nmcli connection edit bridge-br0</code></pre>
+ You will be placed at the <span class="application"><strong>nmcli</strong></span> prompt.
+<pre class="screen">nmcli> <code class="command">set bridge.priority 4096</code>
+nmcli> <code class="command">save</code>
+Connection 'bridge-br0' (79cf6a3e-0310-4a78-b759-bda1cc3eef8d) successfully saved.
+nmcli> <code class="command">quit</code></pre>
+
+ </div><div class="para">
+ See <a class="xref" href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html">Section 2.4, “Using the NetworkManager Command Line Tool, nmcli”</a> for an introduction to <span class="application"><strong>nmcli</strong></span>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Create_a_Network_Bridge.html"><strong>Prev</strong>6.2.2. Create a Network Bridge</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Bridging-additional_resources.html"><strong>Next</strong>6.4. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Config_Using_CLI.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Config_Using_CLI.html
new file mode 100644
index 0000000..c08dbd0
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Config_Using_CLI.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.4. Network Configuration Using the Command Line Interface (CLI)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Introduction_to_Fedora_Networking.html" title="Chapter 1. Introduction to Fedora Networking" /><link rel="prev" href="sec-Interacting_with_NetworkManager.html" title="1.3.2. Interacting with NetworkManager" /><link rel="next" href="sec-Network_Config_Using_nmcli.html" title="1.5. Network Configuration Using NetworkManager's CLI (nmcli)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previou
s"><a accesskey="p" href="sec-Interacting_with_NetworkManager.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Config_Using_nmcli.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Network_Config_Using_CLI"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.4. Network Configuration Using the Command Line Interface (CLI)</h2></div></div></div><div class="para">
+ </div><div class="para">
+ The commands for the <span class="application"><strong>ip</strong></span> utility, sometimes referred to as <span class="package">iproute2</span> after the upstream package name, are documented in the <code class="filename">man ip(8)</code> page. The package name in Fedora is <span class="package">iproute</span>. If necessary, you can check that the <span class="application"><strong>ip</strong></span> utility is installed by checking its version number as follows:
+ </div><pre class="screen">~]$ <code class="command">ip -V</code>
+ip utility, iproute2-ss130716</pre><div class="para">
+ The <span class="application"><strong>ip</strong></span> commands can be used to add and remove addresses and routes to interfaces in parallel with <span class="application"><strong>NetworkManager</strong></span>, which will preserve them and recognize them in <span class="application"><strong>nmcli</strong></span>, <span class="application"><strong>nmtui</strong></span>, <span class="application"><strong>control-center</strong></span>, and the D-Bus API.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that <span class="application"><strong>ip</strong></span> commands given on the command line will not persist after a system restart.
+ </div></div></div><div class="para">
+ Examples of using the command line and configuration files for each task are included after explaining the use of one of the graphical user interfaces to <span class="application"><strong>NetworkManager</strong></span>, namely, <span class="application"><strong>control-center</strong></span> and <span class="application"><strong>nm-connection-editor</strong></span>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Interacting_with_NetworkManager.html"><strong>Prev</strong>1.3.2. Interacting with NetworkManager</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Config_Using_nmcli.html"><strong>Next</strong>1.5. Network Configuration Using NetworkManager's...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Config_Using_nmcli.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Config_Using_nmcli.html
new file mode 100644
index 0000000..8a043e1
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Config_Using_nmcli.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.5. Network Configuration Using NetworkManager's CLI (nmcli)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Introduction_to_Fedora_Networking.html" title="Chapter 1. Introduction to Fedora Networking" /><link rel="prev" href="sec-Network_Config_Using_CLI.html" title="1.4. Network Configuration Using the Command Line Interface (CLI)" /><link rel="next" href="sec-NetworkManager_and_the_Network_Scripts.html" title="1.6. NetworkManager and the Network Scripts" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="sec-Network_Config_Using_CLI.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-NetworkManager_and_the_Network_Scripts.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Network_Config_Using_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.5. Network Configuration Using NetworkManager's CLI (nmcli)</h2></div></div></div><div class="para">
+ </div><div class="para">
+ The <span class="application"><strong>NetworkManager</strong></span> command-line tool, <span class="application"><strong>nmcli</strong></span>, provides a command line way to configure networking by controlling <span class="application"><strong>NetworkManager</strong></span>. It is installed, along with <span class="application"><strong>NetworkManager</strong></span>, by default. If required, for details on how to verify that <span class="application"><strong>NetworkManager</strong></span> is running, see <a class="xref" href="sec-Installing_NetworkManager.html#sec-The_NetworkManager_Daemon">Section 1.3.1, “The NetworkManager Daemon”</a>.
+ </div><div class="para">
+ Examples of using the <span class="application"><strong>nmcli</strong></span> tool for each task will be included where possible, after explaining the use of graphical user interfaces and other command line methods. See <a class="xref" href="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html">Section 2.4, “Using the NetworkManager Command Line Tool, nmcli”</a> for an introduction to <span class="application"><strong>nmcli</strong></span>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Network_Config_Using_CLI.html"><strong>Prev</strong>1.4. Network Configuration Using the Command Line...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-NetworkManager_and_the_Network_Scripts.html"><strong>Next</strong>1.6. NetworkManager and the Network Scripts</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Configuration_Using_sysconfig_Files.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Configuration_Using_sysconfig_Files.html
new file mode 100644
index 0000000..12bda39
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Configuration_Using_sysconfig_Files.html
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.7. Network Configuration Using sysconfig Files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Introduction_to_Fedora_Networking.html" title="Chapter 1. Introduction to Fedora Networking" /><link rel="prev" href="sec-NetworkManager_and_the_Network_Scripts.html" title="1.6. NetworkManager and the Network Scripts" /><link rel="next" href="sec-Introduction_to_Fedora_Networking-additional_resources.html" title="1.8. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="pre
vious"><a accesskey="p" href="sec-NetworkManager_and_the_Network_Scripts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Introduction_to_Fedora_Networking-additional_resources.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Network_Configuration_Using_sysconfig_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.7. Network Configuration Using sysconfig Files</h2></div></div></div><div class="para">
+ The <code class="filename">/etc/sysconfig/</code> directory is a location for configuration files and scripts. Most network configuration information is stored there, with the exception of VPN, mobile broadband and PPPoE configuration, which are stored in <code class="filename">/etc/NetworkManager/</code> subdirectories. Interface specific information for example, is stored in <code class="filename">ifcfg</code> files in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory.
+ </div><div class="para">
+ The file <code class="filename">/etc/sysconfig/network</code> is for global settings. Information for VPNs, mobile broadband and PPPoE connections is stored in <code class="filename">/etc/NetworkManager/system-connections/</code>.
+ </div><div class="para">
+ In Fedora, when you edit an <code class="filename">ifcfg</code> file, <span class="application"><strong>NetworkManager</strong></span> is not automatically aware of the change and has to be prompted to notice the change. If you use one of the tools to update <span class="application"><strong>NetworkManager</strong></span> profile settings, then <span class="application"><strong>NetworkManager</strong></span> does not implement those changes until you reconnect using that profile. For example, if configuration files have been changed using an editor, <span class="application"><strong>NetworkManager</strong></span> must be told to read the configuration files again. To do that, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">nmcli connection reload</code></pre>
+ The above command reads all connection profiles. Alternatively, to reload only one changed file, <code class="filename">ifcfg-<em class="replaceable"><code>ifname</code></em></code>, issue a command as follows:
+<pre class="screen">~]# <code class="command">nmcli con load /etc/sysconfig/network-scripts/ifcfg-<em class="replaceable"><code>ifname</code></em></code></pre>
+ The command accepts multiple file names. These commands require <code class="systemitem">root</code> privileges. For more information on user privileges and gaining privileges, see the <em class="citetitle">Fedora 20 System Administrator's Guide</em> and the <code class="filename">su(1)</code> and <code class="filename">sudo(8)</code> man pages.
+ </div><div class="para">
+ Changes made using tools such as <span class="application"><strong>nmcli</strong></span> do not require a reload but do require the associated interface to be put down and then up again. That can be done by using commands in the following format: <pre class="synopsis">nmcli dev disconnect <em class="replaceable"><code>interface-name</code></em></pre> Followed by: <pre class="synopsis">nmcli con up <em class="replaceable"><code>interface-name</code></em></pre>
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> does not trigger any of the network scripts, though the network scripts will try to trigger <span class="application"><strong>NetworkManager</strong></span> if it is running when <code class="filename">ifup</code> commands are used. See <a class="xref" href="sec-NetworkManager_and_the_Network_Scripts.html">Section 1.6, “NetworkManager and the Network Scripts”</a> for an explanation of the network scripts.
+ </div><div class="para">
+ The <code class="filename">ifup</code> script is a generic script which does a few things and then calls interface-specific scripts like <code class="filename">ifup-ethX</code>, <code class="filename">ifup-wireless</code>, <code class="filename">ifup-ppp</code>, and so on. When a user runs <code class="command">ifup eth0</code> manually, the following occurs:
+ <div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <code class="filename">ifup</code> looks for a file called <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth0</code>;
+ </div></li><li class="listitem"><div class="para">
+ if the <code class="filename">ifcfg</code> file exists, <code class="filename">ifup</code> looks for the <code class="option">TYPE</code> key in that file to determine which type-specific script to call;
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ifup</code> calls <code class="filename">ifup-wireless</code> or <code class="filename">ifup-eth</code> or <code class="filename">ifup-XXX</code> based on <code class="option">TYPE</code>;
+ </div></li><li class="listitem"><div class="para">
+ the type-specific scripts do type-specific setup;
+ </div></li><li class="listitem"><div class="para">
+ and then the type-specific scripts let common functions perform <code class="systemitem">IP</code>-related tasks like <code class="systemitem">DHCP</code> or static setup.
+ </div></li></ol></div>
+
+ </div><div class="para">
+ On bootup, <code class="filename">/etc/init.d/network</code> reads through all the <code class="filename">ifcfg</code> files and for each one that has <code class="command">ONBOOT=yes</code>, it checks whether <span class="application"><strong>NetworkManager</strong></span> is already starting the DEVICE from that <code class="filename">ifcfg</code> file. If <span class="application"><strong>NetworkManager</strong></span> is starting that device or has already started it, nothing more is done for that file, and the next <code class="command">ONBOOT=yes</code> file is checked. If <span class="application"><strong>NetworkManager</strong></span> is not yet starting that device, the initscripts will continue with their traditional behavior and call <code class="filename">ifup</code> for that <code class="filename">ifcfg</code> file.
+ </div><div class="para">
+ The end result is that any <code class="filename">ifcfg</code> file that has <code class="command">ONBOOT=yes</code> is expected to be started on system bootup, either by <span class="application"><strong>NetworkManager</strong></span> or by the initscripts. This ensures that some legacy network types which <span class="application"><strong>NetworkManager</strong></span> does not handle (such as ISDN or analog dialup modems) as well as any new application not yet supported by <span class="application"><strong>NetworkManager</strong></span> are still correctly started by the initscripts even though <span class="application"><strong>NetworkManager</strong></span> is unable to handle them.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ It is recommended not to store backup <code class="filename">ifcfg</code> files in the same location as the live ones. The script literally does <code class="command">ifcfg-*</code> with an exclude only for these extensions: <code class="filename">.old</code>, <code class="filename">.orig</code>, <code class="filename">.rpmnew</code>, <code class="filename">.rpmorig</code>, and <code class="filename">.rpmsave</code>. The best way is not to store backup files anywhere within the <code class="filename">/etc/</code> directory.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-NetworkManager_and_the_Network_Scripts.html"><strong>Prev</strong>1.6. NetworkManager and the Network Scripts</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Introduction_to_Fedora_Networking-additional_resources.html"><strong>Next</strong>1.8. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Teaming-additional_resources.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Teaming-additional_resources.html
new file mode 100644
index 0000000..56e7274
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Network_Teaming-additional_resources.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.14. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Teaming.html" title="Chapter 5. Configure Network Teaming" /><link rel="prev" href="sec-Configure_Network_Teaming_Using_nmcli.html" title="5.13. Configure Network Teaming Using nmcli" /><link rel="next" href="sec-teamd_docs-online.html" title="5.14.2. Online Documentation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_Network
_Teaming_Using_nmcli.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-teamd_docs-online.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Network_Teaming-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.14. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding network teaming.
+ </div><div class="section" id="sec-teamd-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.14.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">teamd(8)</code> man page — Describes the <code class="systemitem">teamd</code> service.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">teamdctl(8)</code> man page — Describes the <code class="systemitem">teamd</code> control tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">teamd.conf(5)</code> man page — Describes the <code class="systemitem">teamd</code> configuration file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">teamnl(8)</code> man page — Describes the <code class="systemitem">teamd</code> Netlink library.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">bond2team(1)</code> man page — Describes a tool to convert bonding options to team.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configure_Network_Teaming_Using_nmcli.html"><strong>Prev</strong>5.13. Configure Network Teaming Using nmcli</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-teamd_docs-online.html"><strong>Next</strong>5.14.2. Online Documentation</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Preface-About_this_book.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Preface-About_this_book.html
new file mode 100644
index 0000000..847ea8f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Preface-About_this_book.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2. About This Book</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="pr01.html" title="Preface" /><link rel="prev" href="pr01.html" title="Preface" /><link rel="next" href="sec-Whats-New.html" title="3. What's new in Fedora 20" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Whats-New.html"><strong>Next</strong></a></li></ul><div class="section" id=
"sec-Preface-About_this_book"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2. About This Book</h2></div></div></div><div class="para">
+ The <em class="citetitle">Networking Guide</em> is based on the networking material in the <a href="https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/index.html"><em class="citetitle">Red Hat Enterprise Linux 6 Deployment Guide</em></a>. It also retains the information on <code class="systemitem">DHCP</code> and <code class="systemitem">DNS</code> servers from the <a class="xref" href="part-Servers.html">Part II, “Servers”</a> section. Most of the non-networking related material from the <em class="citetitle">Red Hat Enterprise Linux 6 Deployment Guide</em> guide can now be found in the <em class="citetitle">Fedora 20 System Administrator's Guide</em> except for reference material, such as that found in the appendices of the Deployment Guide.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01.html"><strong>Prev</strong>Preface</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Whats-New.html"><strong>Next</strong>3. What's new in Fedora 20</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Preface-Book_Organization.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Preface-Book_Organization.html
new file mode 100644
index 0000000..b61140c
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Preface-Book_Organization.html
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4. How to Read this Book</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="pr01.html" title="Preface" /><link rel="prev" href="sec-Whats-New.html" title="3. What's new in Fedora 20" /><link rel="next" href="pr01s05.html" title="5. Document Conventions" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Whats-New.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pr01s05.html"><strong>Next</strong></a></li></ul><
div class="section" id="sec-Preface-Book_Organization"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4. How to Read this Book</h2></div></div></div><div class="para">
+ This manual is divided into the following main categories:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a class="xref" href="part-Networking.html">Part I, “Networking”</a> </span></dt><dd><div class="para">
+ This part describes how to configure the network on Fedora.
+ </div><div class="para">
+ <a class="xref" href="ch-Introduction_to_Fedora_Networking.html">Chapter 1, <em>Introduction to Fedora Networking</em></a> explains the default networking service, <span class="application"><strong>NetworkManager</strong></span>, and the various graphical and command-line tools that can be used to interact with <span class="application"><strong>NetworkManager</strong></span>. These include, an associated command-line configuration tool, <span class="application"><strong>nmcli</strong></span>, and two graphical user interface tools, <span class="application"><strong>control-center</strong></span> and <span class="application"><strong>nm-connection-editor</strong></span>. Read this chapter to learn more about the many ways the <span class="application"><strong>NetworkManager</strong></span> daemon can be used.
+ </div><div class="para">
+ <a class="xref" href="ch-Configure_Networking.html">Chapter 2, <em>Configure Networking</em></a> covers static and dynamic interface settings, selecting network configuration methods, using <span class="application"><strong>NetworkManager</strong></span> with graphical and command-line user interfaces. Read this chapter to learn about configuring network connections.
+ </div><div class="para">
+ <a class="xref" href="ch-Configure_Host_Names.html">Chapter 3, <em>Configure Host Names</em></a> covers static, pretty, and transient host names and their configuration using <span class="application"><strong>hostnamectl</strong></span>. Read this chapter to learn more about configuring host names on local and remote systems.
+ </div><div class="para">
+ <a class="xref" href="ch-Configure_Network_Bonding.html">Chapter 4, <em>Configure Network Bonding</em></a> covers the configuring and use of bonded network connections. Read this chapter to learn about the configuring of network bonds using graphical and command-line user interfaces.
+ </div><div class="para">
+ <a class="xref" href="ch-Configure_Network_Teaming.html">Chapter 5, <em>Configure Network Teaming</em></a> covers the configuring and use of teamed network connections. Read this chapter to learn about the configuring of network teams using graphical and command-line user interfaces.
+ </div><div class="para">
+ <a class="xref" href="ch-Configure_Network_Bridging.html">Chapter 6, <em>Configure Network Bridging</em></a> covers the configuring and use of network bridges. Read this chapter to learn about the configuring of network bridges using graphical and command-line user interfaces.
+ </div><div class="para">
+ <a class="xref" href="ch-Configure_802_1Q_VLAN_Tagging.html">Chapter 7, <em>Configure 802.1Q VLAN tagging</em></a> covers the configuring and use of virtual private networks, VLANs, according to the 802.1Q standard. Read this chapter to learn about the configuring of VLANs using graphical and command-line user interfaces.
+ </div><div class="para">
+ <a class="xref" href="ch-Consistent_Network_Device_Naming.html">Chapter 8, <em>Consistent Network Device Naming</em></a> covers consistent network device naming for network interfaces, a feature that changes the name of network interfaces on a system in order to make locating and differentiating the interfaces easier. Read this chapter to learn about this feature and how to enable or disable it.
+ </div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="part-Servers.html">Part II, “Servers”</a></span></dt><dd><div class="para">
+ This part discusses how to set up servers normally required for networking.
+ </div><div class="para">
+ <a class="xref" href="ch-DHCP_Servers.html">Chapter 9, <em>DHCP Servers</em></a> covers the installation of a Dynamic Host Configuration Protocol (<code class="systemitem">DHCP</code>) server and client. Read this chapter if you need to configure <code class="systemitem">DHCP</code> on your system.
+ </div><div class="para">
+ <a class="xref" href="ch-DNS_Servers.html">Chapter 10, <em>DNS Servers</em></a> covers the Domain Name System (<code class="systemitem">DNS</code>), explains how to install, configure, run, and administer the <span class="application"><strong>BIND</strong></span> <code class="systemitem">DNS</code> server. Read this chapter if you need to configure a <code class="systemitem">DNS</code> server on your system.
+ </div></dd></dl></div><div class="para">
+ For topics related to network configuration but not listed above, such as configuring GRUB to enable serial links and the use of virtual console terminals, see the <em class="citetitle">Fedora 20 System Administrator's Guide</em>.
+ </div><div class="para">
+ For topics related to servers but not listed above, such as configuring Network Time Protocol (<code class="systemitem">NTP</code>) and Precision Time Protocol (<code class="systemitem">PTP</code>), see the <em class="citetitle">Fedora 20 System Administrator's Guide</em>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Whats-New.html"><strong>Prev</strong>3. What's new in Fedora 20</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pr01s05.html"><strong>Next</strong>5. Document Conventions</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Preface-Feedback.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Preface-Feedback.html
new file mode 100644
index 0000000..6d4f6a9
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Preface-Feedback.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6. Feedback</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="pr01.html" title="Preface" /><link rel="prev" href="pr01s05s03.html" title="5.3. Notes and Warnings" /><link rel="next" href="pref-Acknowledgments.html" title="7. Acknowledgments" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s05s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pref-Acknowledgments.html"><strong>Next</strong></a
></li></ul><div xml:lang="en-US" class="section" id="sec-Preface-Feedback" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6. Feedback</h2></div></div></div><a id="idm225488780304" class="indexterm"></a><div class="para">
+ If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in <a href="http://bugzilla.redhat.com/">Bugzilla</a> against the product <span class="application"><strong>Fedora Documentation</strong></span>.
+ </div><div class="para">
+ When submitting a bug report, be sure to provide the following information:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Manual's identifier: <code class="literal">networking-guide</code>
+ </div></li><li class="listitem"><div class="para">
+ Version number: <code class="literal">20</code>
+ </div></li></ul></div><div class="para">
+ If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s05s03.html"><strong>Prev</strong>5.3. Notes and Warnings</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pref-Acknowledgments.html"><strong>Next</strong>7. Acknowledgments</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Remove_a_Port_From_a_Network_Team.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Remove_a_Port_From_a_Network_Team.html
new file mode 100644
index 0000000..5a4c567
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Remove_a_Port_From_a_Network_Team.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.11.2. Remove a Port From a Network Team</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Controlling_teamd_with_teamdctl.html" title="5.11. Controlling teamd with teamdctl" /><link rel="prev" href="sec-Controlling_teamd_with_teamdctl.html" title="5.11. Controlling teamd with teamdctl" /><link rel="next" href="sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team.html" title="5.11.3. Apply a Configuration to a Port in a Network Team" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class
="previous"><a accesskey="p" href="sec-Controlling_teamd_with_teamdctl.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Remove_a_Port_From_a_Network_Team"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.11.2. Remove a Port From a Network Team</h3></div></div></div><div class="para">
+ To remove an interface <span class="interface">em1</span> from a network team <span class="interface">team0</span>, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamdctl team0 port remove em1</code></pre>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Controlling_teamd_with_teamdctl.html"><strong>Prev</strong>5.11. Controlling teamd with teamdctl</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team.html"><strong>Next</strong>5.11.3. Apply a Configuration to a Port in a Netw...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team.html
new file mode 100644
index 0000000..1ccb6b5
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.7. Selecting Interfaces to Use as Ports for a Network Team</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Teaming.html" title="Chapter 5. Configure Network Teaming" /><link rel="prev" href="sec-Converting_a_Bond_to_a_Team.html" title="5.6. Converting a Bond to a Team" /><link rel="next" href="sec-Selecting_Network_Team_Configuration_Methods.html" title="5.8. Selecting Network Team Configuration Methods" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p"
href="sec-Converting_a_Bond_to_a_Team.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Selecting_Network_Team_Configuration_Methods.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.7. Selecting Interfaces to Use as Ports for a Network Team</h2></div></div></div><div class="para">
+ To view the available interfaces, issue the following command:
+<pre class="screen">~]$ <code class="command">ip link show</code>
+1: lo: <LOOPBACK,UP,LOWER_UP > mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP > mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
+ link/ether 52:54:00:6a:02:8a brd ff:ff:ff:ff:ff:ff
+3: em2: <BROADCAST,MULTICAST,UP,LOWER_UP > mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
+link/ether 52:54:00:9b:6d:2a brd ff:ff:ff:ff:ff:ff</pre>
+ From the available interfaces, determine which are suitable for adding to your network team and then proceed to <a class="xref" href="sec-Selecting_Network_Team_Configuration_Methods.html">Section 5.8, “Selecting Network Team Configuration Methods”</a>
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The Team developers prefer the term <span class="quote">“<span class="quote">port</span>”</span> rather than <span class="quote">“<span class="quote">slave</span>”</span>, however <span class="application"><strong>NetworkManager</strong></span> uses the term <span class="quote">“<span class="quote">team-slave</span>”</span> to refer to interfaces that make up a team.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Converting_a_Bond_to_a_Team.html"><strong>Prev</strong>5.6. Converting a Bond to a Team</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Selecting_Network_Team_Configuration_Methods.html"><strong>Next</strong>5.8. Selecting Network Team Configuration Methods</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Selecting_Network_Team_Configuration_Methods.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Selecting_Network_Team_Configuration_Methods.html
new file mode 100644
index 0000000..13ddd9c
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Selecting_Network_Team_Configuration_Methods.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.8. Selecting Network Team Configuration Methods</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Teaming.html" title="Chapter 5. Configure Network Teaming" /><link rel="prev" href="sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team.html" title="5.7. Selecting Interfaces to Use as Ports for a Network Team" /><link rel="next" href="sec-Creating_a_Network_Team_Using_a_GUI.html" title="5.9. Creating a Network Team Using a GUI" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><
li class="previous"><a accesskey="p" href="sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Creating_a_Network_Team_Using_a_GUI.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Selecting_Network_Team_Configuration_Methods"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.8. Selecting Network Team Configuration Methods</h2></div></div></div><div class="para">
+ <span class="bold bold"><strong>To configure a network team using a graphical user interface</strong></span>, see <a class="xref" href="sec-Creating_a_Network_Team_Using_a_GUI.html">Section 5.9, “Creating a Network Team Using a GUI”</a>
+ </div><div class="para">
+ <span class="bold bold"><strong>To create a network team using the Team daemon</strong></span>, <code class="systemitem">teamd</code>, proceed to <a class="xref" href="sec-Configure_a_Network_Team_Using-the_Command_Line.html#sec-Creating_a_Network_Team_Using_teamd">Section 5.10.1, “Creating a Network Team Using teamd”</a>.
+ </div><div class="para">
+ <span class="bold bold"><strong>To create a network team using configuration files</strong></span>, proceed to <a class="xref" href="sec-Creating_a_Network_Team_Using_ifcfg_Files.html">Section 5.10.2, “Creating a Network Team Using ifcfg Files”</a>.
+ </div><div class="para">
+ <span class="bold bold"><strong>To create a network team using the command-line tool</strong></span>, <span class="application"><strong>nmcli</strong></span>, proceed to <a class="xref" href="sec-Configure_Network_Teaming_Using_nmcli.html">Section 5.13, “Configure Network Teaming Using nmcli”</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Selecting_Interfaces_to_Use_as_Port_for_a_Network_Team.html"><strong>Prev</strong>5.7. Selecting Interfaces to Use as Ports for a N...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Creating_a_Network_Team_Using_a_GUI.html"><strong>Next</strong>5.9. Creating a Network Team Using a GUI</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl.html
new file mode 100644
index 0000000..f84ca1d
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.9. Setting the Active Port Options of a Team Using teamnl</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_a_Network_Team_Using-the_Command_Line.html" title="5.10. Configure a Network Team Using the Command Line" /><link rel="prev" href="sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl.html" title="5.10.8. Viewing the Active Port Options of a Team Using teamnl" /><link rel="next" href="sec-Controlling_teamd_with_teamdctl.html" title="5.11. Controlling teamd with teamdctl" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /><
/a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Controlling_teamd_with_teamdctl.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.9. Setting the Active Port Options of a Team Using teamnl</h3></div></div></div><div class="para">
+ To set the <code class="option">activeport</code> option in a network team, using the <span class="application"><strong>teamnl</strong></span> utility, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamnl team0 setoption activeport 5</code></pre>
+ To check the change in team port options, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamnl team0 getoption activeport</code>
+5</pre>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl.html"><strong>Prev</strong>5.10.8. Viewing the Active Port Options of a Team...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Controlling_teamd_with_teamdctl.html"><strong>Next</strong>5.11. Controlling teamd with teamdctl</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Static-Routes_and_the_Default_Gateway.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Static-Routes_and_the_Default_Gateway.html
new file mode 100644
index 0000000..7066229
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Static-Routes_and_the_Default_Gateway.html
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.3. Static Routes and the Default Gateway</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Using_the_Command_Line_Interface.html" title="2.3. Using the Command Line Interface (CLI)" /><link rel="prev" href="sec-Configuring_a_Network_Interface_Using_ip_commands.html" title="2.3.2. Configuring a Network Interface Using ip Commands" /><link rel="next" href="sec-Configuring_Static_Routes_in_ifcfg_files.html" title="2.3.4. Configuring Static Routes in ifcfg files" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul
class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_a_Network_Interface_Using_ip_commands.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Static_Routes_in_ifcfg_files.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Static-Routes_and_the_Default_Gateway"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.3. Static Routes and the Default Gateway</h3></div></div></div><div class="para">
+ Static routes are for traffic that must not, or should not, go through the default gateway. Routing is often handled by devices on the network dedicated to routing (although any device can be configured to perform routing). Therefore, it is often not necessary to configure static routes on Fedora servers or clients. Exceptions include traffic that must pass through an encrypted VPN tunnel or traffic that should take a specific route for reasons of cost or security. The default gateway is for any and all traffic which is not destined for the local network and for which no preferred route is specified in the routing table. The default gateway is traditionally a dedicated network router.
+ </div><h4 id="bh-networkscripts-static-routes"> Configuring Static Routes Using the Command Line </h4><a id="idm225431702160" class="indexterm"></a><div class="para">
+ If static routes are required, they can be added to the routing table by means of the <code class="command">ip route add</code> command and removed using the <code class="command">ip route del</code> command. The more frequently used <code class="command">ip route</code> commands take the following form: <pre class="synopsis">ip route [<span class="optional"> add | del | change | append | replace </span>] <em class="replaceable"><code>destination-address</code></em></pre> See the <code class="filename">ip-route(8)</code> man page for more details on the options and formats.
+ </div><div class="para">
+ Use the <code class="command">ip route</code> command without options to display the <code class="systemitem">IP</code> routing table. For example:
+<pre class="screen">~]$ ip route
+default via 192.168.122.1 dev eth1 proto static metric 1024
+192.168.122.0/24 dev eth1 proto kernel scope link src 192.168.122.107
+192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.126</pre>
+ </div><div class="para">
+ To add a static route to a host address, in other words to a single <code class="systemitem">IP</code> address, issue a command as <code class="systemitem">root</code>:
+<pre class="screen">ip route add <em class="replaceable"><code>192.0.2.1</code></em> via <em class="replaceable"><code>10.0.0.1</code></em> [<span class="optional"><code class="option">dev</code> <em class="replaceable"><code>ifname</code></em></span>]</pre>
+ Where <em class="replaceable"><code>192.0.2.1</code></em> is the <code class="systemitem">IP</code> address of the host in dotted decimal notation, <em class="replaceable"><code>10.0.0.1</code></em> is the next hop address and <em class="replaceable"><code>ifname</code></em> is the exit interface leading to the next hop.
+ </div><div class="para">
+ To add a static route to a network, in other words to an <code class="systemitem">IP</code> address representing a range of <code class="systemitem">IP</code> addresses, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">ip route add <em class="replaceable"><code>192.0.2.0/24</code></em> via <em class="replaceable"><code>10.0.0.1</code></em> [<span class="optional"><code class="option">dev</code> <em class="replaceable"><code>ifname</code></em></span>]</pre>
+ where <em class="replaceable"><code>192.0.2.0</code></em> is the <code class="systemitem">IP</code> address of the destination network in dotted decimal notation and <em class="replaceable"><code>/24</code></em> is the network prefix. The network prefix is the number of enabled bits in the subnet mask. This format of network address slash network prefix length is sometimes referred to as <em class="firstterm">classless inter-domain routing</em> (<acronym class="acronym">CIDR</acronym>) notation.
+ </div><div class="para">
+ Static route configuration can be stored per-interface in a <code class="filename">/etc/sysconfig/network-scripts/route-<em class="replaceable"><code>interface</code></em></code> file. For example, static routes for the <span class="interface">eth0</span> interface would be stored in the <code class="filename">/etc/sysconfig/network-scripts/route-eth0</code> file. The <code class="filename">route-<em class="replaceable"><code>interface</code></em></code> file has two formats: <span class="application"><strong>ip</strong></span> command arguments and network/netmask directives. These are described below.
+ </div><div class="para">
+ See the <code class="filename">ip-route(8)</code> man page for more information on the <code class="command">ip route</code> command.
+ </div><h4 id="bh-networkscripts-default-gateway"> Configuring The Default Gateway </h4><a id="idm225446813488" class="indexterm"></a><div class="para">
+ The default gateway is determined by the network scripts which parse the <code class="filename">/etc/sysconfig/network</code> file first and then the network interface <code class="literal">ifcfg</code> files for interfaces that are <span class="quote">“<span class="quote">up</span>”</span>. The <code class="literal">ifcfg</code> files are parsed in numerically ascending order, and the last GATEWAY directive to be read is used to compose a default route in the routing table.
+ </div><div class="para">
+ The default route can thus be indicated by means of the GATEWAY directive and can be specified either globally or in interface-specific configuration files. Specifying the gateway globally has certain advantages in static networking environments, especially if more than one network interface is present. It can make fault finding simpler if applied consistently.
+ </div><div class="para">
+ In dynamic network environments, where mobile hosts are managed by <span class="application"><strong>NetworkManager</strong></span>, gateway information is likely to be interface specific and is best left to be assigned by <code class="systemitem">DHCP</code>. In special cases where it is necessary to influence <span class="application"><strong>NetworkManager</strong></span>'s selection of the exit interface to be used to reach a gateway, make use of the <code class="command">DEFROUTE=no</code> command in the <code class="literal">ifcfg</code> files for those interfaces which do not lead to the default gateway.
+ </div><div class="para">
+ Global default gateway configuration is stored in the <code class="filename">/etc/sysconfig/network</code> file. This file specifies gateway and host information for all network interfaces.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_a_Network_Interface_Using_ip_commands.html"><strong>Prev</strong>2.3.2. Configuring a Network Interface Using ip C...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Static_Routes_in_ifcfg_files.html"><strong>Next</strong>2.3.4. Configuring Static Routes in ifcfg files</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-System-wide_and_Private_Connection_Profiles.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-System-wide_and_Private_Connection_Profiles.html
new file mode 100644
index 0000000..341e972
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-System-wide_and_Private_Connection_Profiles.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.4. System-wide and Private Connection Profiles</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html" title="2.2. Using NetworkManager with the GNOME Graphical User Interface" /><link rel="prev" href="sec-Connecting_to_a_Network_Automatically.html" title="2.2.3. Connecting to a Network Automatically" /><link rel="next" href="sec-Configuring_a_Wired_Ethernet_Connection.html" title="2.2.5. Configuring a Wired (Ethernet) Connection" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documen
tation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Connecting_to_a_Network_Automatically.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_a_Wired_Ethernet_Connection.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-System-wide_and_Private_Connection_Profiles"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.4. System-wide and Private Connection Profiles</h3></div></div></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> stores all <em class="firstterm">connection profiles</em>. A profile is a named collection of settings that can be applied to an interface. <span class="application"><strong>NetworkManager</strong></span> stores these connection profiles for system-wide use (<em class="firstterm">system connections</em>), as well as all <em class="firstterm">user connection</em> profiles. Access to the connection profiles is controlled by permissions which are stored by <span class="application"><strong>NetworkManager</strong></span>. See the <code class="filename">nm-settings(5)</code> man page for more information on the <code class="option">connection</code> settings <code class="option">permissions</code> property. The permissions correspond to the <code class="command">USERS</code> directive in the <code class="filename">ifcfg</code> files. If the <code class="command">USERS</code> directive is not present, the network
profile will be available to all users. As an example, the following command in an <code class="filename">ifcfg</code> file will make the connection available only to the users listed: <pre class="synopsis">USERS="joe bob alice"</pre> This can also be set using graphical user interface tools. In <span class="application"><strong>nm-connection-editor</strong></span>, there is the corresponding <span class="guilabel"><strong>All users may connect to this network</strong></span> check box on the <span class="guilabel"><strong>General</strong></span> tab, and in the GNOME <span class="application"><strong>control-center</strong></span> Network settings Identity window, there is the <span class="guilabel"><strong>Make available to other users</strong></span> check box.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span>'s default policy is to allow all users to create and modify system-wide connections. Profiles that should be available at boot time cannot be private because they will not be visible until the user logs in. For example, if user <code class="systemitem">user</code> creates a connection profile <code class="literal">user-em2</code> with the <span class="guilabel"><strong>Connect Automatically</strong></span> check box selected but with the <span class="guilabel"><strong>Make available to other users</strong></span> not selected, then the connection will not be available at boot time.
+ </div><div class="para">
+ To restrict connections and networking, there are two options which can be used alone or in combination:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Clear the <span class="guilabel"><strong>Make available to other users</strong></span> check box, which changes the connection to be modifiable and usable only by the user doing the changing.
+ </div></li><li class="listitem"><div class="para">
+ Use the <span class="application"><strong>polkit</strong></span> framework to restrict permissions of general network operations on a per-user basis.
+ </div></li></ul></div>
+ The combination of these two options provides fine-grained security and control over networking. See the <code class="filename">polkit(8)</code> man page for more information on <span class="application"><strong>polkit</strong></span>.
+ </div><div class="para">
+ Note that VPN connections are <span class="bold bold"><strong>always</strong></span> created as private-per-user, since they are assumed to be more private than a Wi-Fi or Ethernet connection.
+ </div><div class="procedure"><h6>Procedure 2.2. Changing a Connection to Be User-specific Instead of System-Wide, or Vice Versa</h6><div class="para">
+ Depending on the system's policy, you may need root privileges on the system in order to change whether a connection is user-specific or system-wide.
+ </div><ol class="1"><li class="step"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears.
+ </div></li><li class="step"><div class="para">
+ Select the network interface from the left-hand-side menu.
+ </div></li><li class="step"><div class="para">
+ Click on the gear wheel icon of a connection profile on the right-hand side menu. If you have only one profile associated with the selected interface the gear wheel icon will be in the lower right-hand-side corner. The <span class="guilabel"><strong>Network</strong></span> details window appears.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Identity</strong></span> menu entry on the left. The <span class="guilabel"><strong>Network</strong></span> window changes to the identity view.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Make available to other users</strong></span> check box to cause <span class="application"><strong>NetworkManager</strong></span> to make the connection available system-wide. Depending on system policy, you may then be prompted for an administrator or <code class="systemitem">root</code> password by the <span class="application"><strong>polkit</strong></span> application. If so, enter the appropriate password to finalize the changes.
+ </div><div class="para">
+ Conversely, clear the <span class="guilabel"><strong>Make available to other users</strong></span> check box to make the connection user-specific.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Connecting_to_a_Network_Automatically.html"><strong>Prev</strong>2.2.3. Connecting to a Network Automatically</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_a_Wired_Ethernet_Connection.html"><strong>Next</strong>2.2.5. Configuring a Wired (Ethernet) Connection</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces.html
new file mode 100644
index 0000000..f9a1360
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.3. Understanding the Default Behavior of Master and Slave Interfaces</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Teaming.html" title="Chapter 5. Configure Network Teaming" /><link rel="prev" href="sec-Comparison_of_Network_Teaming_to_Bonding.html" title="5.2. Comparison of Network Teaming to Bonding" /><link rel="next" href="sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners.html" title="5.4. Understanding the Network Teaming Daemon and the "Runners"" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a
></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Comparison_of_Network_Teaming_to_Bonding.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.3. Understanding the Default Behavior of Master and Slave Interfaces</h2></div></div></div><div class="para">
+ When controlling teamed port interfaces using the <code class="systemitem">NetworkManager</code> daemon, and especially when fault finding, keep the following in mind:
+ <div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Starting the master interface does not automatically start the port interfaces.
+ </div></li><li class="listitem"><div class="para">
+ Starting a port interface always starts the master interface.
+ </div></li><li class="listitem"><div class="para">
+ Stopping the master interface also stops the port interfaces.
+ </div></li><li class="listitem"><div class="para">
+ A master without ports can start static <code class="systemitem">IP</code> connections.
+ </div></li><li class="listitem"><div class="para">
+ A master without ports waits for ports when starting <code class="systemitem">DHCP</code> connections.
+ </div></li><li class="listitem"><div class="para">
+ A master with a <code class="systemitem">DHCP</code> connection waiting for ports completes when a port with a carrier is added.
+ </div></li><li class="listitem"><div class="para">
+ A master with a <code class="systemitem">DHCP</code> connection waiting for ports continues waiting when a port without a carrier is added.
+ </div></li></ol></div>
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The use of direct cable connections without network switches is not supported for teaming. The failover mechanisms described here will not work as expected without the presence of network switches.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Comparison_of_Network_Teaming_to_Bonding.html"><strong>Prev</strong>5.2. Comparison of Network Teaming to Bonding</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners.html"><strong>Next</strong>5.4. Understanding the Network Teaming Daemon and...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Understanding_the_Device_Renaming_Procedure.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Understanding_the_Device_Renaming_Procedure.html
new file mode 100644
index 0000000..b6344f8
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Understanding_the_Device_Renaming_Procedure.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2. Understanding the Device Renaming Procedure</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Consistent_Network_Device_Naming.html" title="Chapter 8. Consistent Network Device Naming" /><link rel="prev" href="ch-Consistent_Network_Device_Naming.html" title="Chapter 8. Consistent Network Device Naming" /><link rel="next" href="sec-Understanding_the_Predictable_Network_Interface_Device_Names.html" title="8.3. Understanding the Predictable Network Interface Device Names" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a
></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Consistent_Network_Device_Naming.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Understanding_the_Predictable_Network_Interface_Device_Names.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Understanding_the_Device_Renaming_Procedure"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.2. Understanding the Device Renaming Procedure</h2></div></div></div><div class="para">
+ The device name procedure in detail is as follows:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ A rule in <code class="filename">/usr/lib/udev/rules.d/60-net.rules</code> instructs the <span class="application"><strong>udev</strong></span> helper utility, <span class="application"><strong>/lib/udev/rename_device</strong></span>, to look into all <code class="filename">/etc/sysconfig/network-scripts/ifcfg-<em class="replaceable"><code>suffix</code></em></code> files. If it finds an <code class="filename">ifcfg</code> file with a <code class="command">HWADDR</code> entry matching the MAC address of an interface it renames the interface to the name given in the <code class="filename">ifcfg</code> file by the <code class="command">DEVICE</code> directive.
+ </div></li><li class="step"><div class="para">
+ A rule in <code class="filename">/usr/lib/udev/rules.d/71-biosdevname.rules</code> instructs <span class="application"><strong>biosdevname</strong></span> to rename the interface according to its naming policy, provided that it was not renamed in a previous step, <span class="application"><strong>biosdevname</strong></span> is installed, and <code class="command">biosdevname=0</code> was not given as a kernel command on the boot command line.
+ </div></li><li class="step"><div class="para">
+ A rule in <code class="filename">/lib/udev/rules.d/75-net-description.rules</code> instructs <span class="application"><strong>udev</strong></span> to fill in the internal <span class="application"><strong>udev</strong></span> device property values ID_NET_NAME_ONBOARD, ID_NET_NAME_SLOT, ID_NET_NAME_PATH, ID_NET_NAME_MAC by examining the network interface device. Note, that some device properties might be undefined.
+ </div></li><li class="step"><div class="para">
+ A rule in <code class="filename">/usr/lib/udev/rules.d/80-net-name-slot.rules</code> instructs <span class="application"><strong>udev</strong></span> to rename the interface, provided that it was not renamed in step 1 or 2, and the kernel parameter <code class="command">net.ifnames=0</code> was not given, according to the following priority: ID_NET_NAME_ONBOARD, ID_NET_NAME_SLOT, ID_NET_NAME_PATH. It falls through to the next in the list, if one is unset. If none of these are set, then the interface will not be renamed.
+ </div></li></ol></div><div class="para">
+ Steps 3 and 4 are implementing the naming schemes 1, 2, 3, and optionally 4, described in <a class="xref" href="ch-Consistent_Network_Device_Naming.html#sec-Naming_Schemes_Hierarchy">Section 8.1, “Naming Schemes Hierarchy”</a>. Step 2 is explained in more detail in <a class="xref" href="sec-Consistent_Network_Device_Naming_Using_biosdevname.html">Section 8.6, “Consistent Network Device Naming Using biosdevname”</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Consistent_Network_Device_Naming.html"><strong>Prev</strong>Chapter 8. Consistent Network Device Naming</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Understanding_the_Predictable_Network_Interface_Device_Names.html"><strong>Next</strong>8.3. Understanding the Predictable Network Interf...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners.html
new file mode 100644
index 0000000..7600e1b
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.4. Understanding the Network Teaming Daemon and the "Runners"</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Teaming.html" title="Chapter 5. Configure Network Teaming" /><link rel="prev" href="sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces.html" title="5.3. Understanding the Default Behavior of Master and Slave Interfaces" /><link rel="next" href="sec-Install_the_Network_Teaming_Daemon.html" title="5.5. Install the Network Teaming Daemon" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a>
</p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Install_the_Network_Teaming_Daemon.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.4. Understanding the Network Teaming Daemon and the "Runners"</h2></div></div></div><div class="para">
+ The Team daemon, <code class="systemitem">teamd</code>, uses <span class="application"><strong>libteam</strong></span> to control one instance of the team driver. This instance of the team driver adds instances of a hardware device driver to form a <span class="quote">“<span class="quote">team</span>”</span> of network links. The team driver presents a network interface, <span class="interface">team0</span> for example, to the other parts of the kernel. The interfaces created by instances of the team driver are given names such as <span class="interface">team0</span>, <span class="interface">team1</span>, and so forth in the documentation. This is for ease of understanding and other names can be used. The logic common to all methods of teaming is implemented by <code class="systemitem">teamd</code>; those functions that are unique to the different load sharing and backup methods, such as round-robin, are implemented by separate units of code referred to as <span class
="quote">“<span class="quote">runners</span>”</span>. Because words such as <span class="quote">“<span class="quote">module</span>”</span> and <span class="quote">“<span class="quote">mode</span>”</span> already have specific meanings in relation to the kernel, the word <span class="quote">“<span class="quote">runner</span>”</span> was chosen to refer to these units of code. The user specifies the runner in the JSON format configuration file and the code is then compiled into an instance of <code class="systemitem">teamd</code> when the instance is created. A runner is not a plug-in because the code for a runner is compiled into an instance of <code class="systemitem">teamd</code> as it is being created. Code could be created as a plug-in for <code class="systemitem">teamd</code> should the need arise.
+ </div><div class="para">
+ The following runners are available at time of writing.
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ broadcast (data is transmitted over all ports)
+ </div></li><li class="listitem"><div class="para">
+ round-robin (data is transmitted over all ports in turn)
+ </div></li><li class="listitem"><div class="para">
+ active-backup (one port or link is used while others are kept as a backup)
+ </div></li><li class="listitem"><div class="para">
+ loadbalance (with active Tx load balancing and BPF-based Tx port selectors)
+ </div></li><li class="listitem"><div class="para">
+ lacp (implements the 802.3ad Link Aggregation Control Protocol)
+ </div></li></ul></div>
+
+ </div><div class="para">
+ In addition, the following link-watchers are available:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>ethtool</strong></span> (Libteam lib uses <span class="application"><strong>ethtool</strong></span> to watch for link state changes). This is the default if no other link-watcher is specified in the configuration file.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>arp_ping</strong></span> (The <span class="application"><strong>arp_ping</strong></span> utility is used to monitor the presence of a far-end hardware address using ARP packets.)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>nsna_ping</strong></span> (Neighbor Advertisements and Neighbor Solicitation from the <code class="systemitem">IPv6</code> Neighbor Discovery protocol are used to monitor the presence of a neighbor's interface)
+ </div></li></ul></div>
+ There are no restrictions in the code to prevent a particular link-watcher from being used with a particular runner, however when using the <span class="application"><strong>lacp</strong></span> runner, <span class="application"><strong>ethtool</strong></span> is the only recommended link-watcher.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Team-Understanding_the_Default_Behavior_of_Master_and_Slave_Interfaces.html"><strong>Prev</strong>5.3. Understanding the Default Behavior of Master...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Install_the_Network_Teaming_Daemon.html"><strong>Next</strong>5.5. Install the Network Teaming Daemon</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Understanding_the_Predictable_Network_Interface_Device_Names.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Understanding_the_Predictable_Network_Interface_Device_Names.html
new file mode 100644
index 0000000..fc3dde7
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Understanding_the_Predictable_Network_Interface_Device_Names.html
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.3. Understanding the Predictable Network Interface Device Names</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Consistent_Network_Device_Naming.html" title="Chapter 8. Consistent Network Device Naming" /><link rel="prev" href="sec-Understanding_the_Device_Renaming_Procedure.html" title="8.2. Understanding the Device Renaming Procedure" /><link rel="next" href="sec-Naming_Scheme_for_Network_Devices_Available_for_Linux_on_System_z.html" title="8.4. Naming Scheme for Network Devices Available for Linux on System z" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt=
"Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Understanding_the_Device_Renaming_Procedure.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Naming_Scheme_for_Network_Devices_Available_for_Linux_on_System_z.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Understanding_the_Predictable_Network_Interface_Device_Names"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.3. Understanding the Predictable Network Interface Device Names</h2></div></div></div><div class="para">
+ The names have two character prefixes based on the type of interface:
+ <div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <code class="literal">en</code> for Ethernet,
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">wl</code> for wireless LAN (WLAN),
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">ww</code> for wireless wide area network (WWAN).
+ </div></li></ol></div>
+
+ </div><div class="para">
+ The names have the following types:
+ <div class="table" id="Device_Name_Types"><h6>Table 8.1. Device Name Types</h6><div class="table-contents"><table summary="Device Name Types" border="1"><colgroup><col width="63%" class="Format" /><col width="38%" class="Description" /></colgroup><thead><tr><th class="">
+ Format
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ o<<em class="replaceable"><code>index</code></em>>
+ </td><td class="">
+ on-board device index number
+ </td></tr><tr><td class="">
+ s<<em class="replaceable"><code>slot></code></em>[f<<em class="replaceable"><code>function></code></em>][d<<em class="replaceable"><code>dev_id</code></em>>]
+ </td><td class="">
+ hotplug slot index number
+ </td></tr><tr><td class="">
+ x<<em class="replaceable"><code>MAC</code></em>>
+ </td><td class="">
+ MAC address
+ </td></tr><tr><td class="">
+ p<<em class="replaceable"><code>bus</code></em>>s<<em class="replaceable"><code>slot</code></em>>[f<<em class="replaceable"><code>function</code></em>>][d<<em class="replaceable"><code>dev_id</code></em>>]
+ </td><td class="">
+ PCI geographical location
+ </td></tr><tr><td class="">
+ p<<em class="replaceable"><code>bus</code></em>>s<<em class="replaceable"><code>slot</code></em>>[f<<em class="replaceable"><code>function</code></em>>][u<<em class="replaceable"><code>port</code></em>>][..][c<<em class="replaceable"><code>config</code></em>>][i<<em class="replaceable"><code>interface</code></em>>]
+ </td><td class="">
+ USB port number chain
+ </td></tr></tbody></table></div></div><br class="table-break" />
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ All multi-function PCI devices will carry the [f<<em class="replaceable"><code>function</code></em>>] number in the device name, including the function 0 device.
+ </div></li><li class="listitem"><div class="para">
+ For USB devices the full chain of port numbers of hubs is composed. If the name gets longer than the maximum number of 15 characters, the name is not exported.
+ </div></li><li class="listitem"><div class="para">
+ The USB configuration descriptors == 1 and USB interface descriptors == 0 values are suppressed (configuration == 1 and interface == 0 are the default values if only one USB configuration or interface exists).
+ </div></li></ul></div>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Understanding_the_Device_Renaming_Procedure.html"><strong>Prev</strong>8.2. Understanding the Device Renaming Procedure</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Naming_Scheme_for_Network_Devices_Available_for_Linux_on_System_z.html"><strong>Next</strong>8.4. Naming Scheme for Network Devices Available ...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Using_Channel_Bonding.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Using_Channel_Bonding.html
new file mode 100644
index 0000000..003c512
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Using_Channel_Bonding.html
@@ -0,0 +1,202 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.4. Using Channel Bonding</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Network_Bonding.html" title="Chapter 4. Configure Network Bonding" /><link rel="prev" href="sec-Creating_Multiple_Bonds.html" title="4.3.5. Creating Multiple Bonds" /><link rel="next" href="sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli.html" title="4.5. Using the NetworkManager Command Line Tool, nmcli" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous
"><a accesskey="p" href="sec-Creating_Multiple_Bonds.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Using_Channel_Bonding"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.4. Using Channel Bonding</h2></div></div></div><a id="idm225439031376" class="indexterm"></a><a id="idm225439029456" class="indexterm"></a><a id="idm225439028016" class="indexterm"></a><a id="idm225439026576" class="indexterm"></a><a id="idm225439025168" class="indexterm"></a><a id="idm225439023760" class="indexterm"></a><a id="idm225439022320" class="indexterm"></a><div class="para">
+ To enhance performance, adjust available module options to ascertain what combination works best. Pay particular attention to the <code class="command">miimon</code> or <code class="command">arp_interval</code> and the <code class="command">arp_ip_target</code> parameters. See <a class="xref" href="sec-Using_Channel_Bonding.html#s3-modules-bonding-directives">Section 4.4.1, “Bonding Module Directives”</a> for a list of available options and how to quickly determine the best ones for your bonded interface.
+ </div><div class="section" id="s3-modules-bonding-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.4.1. Bonding Module Directives</h3></div></div></div><a id="idm225446648768" class="indexterm"></a><a id="idm225446646880" class="indexterm"></a><a id="idm225446644992" class="indexterm"></a><div class="para">
+ It is a good idea to test which channel bonding module parameters work best for your bonded interfaces before adding them to the <code class="option">BONDING_OPTS="<em class="replaceable"><code>bonding parameters</code></em>"</code> directive in your bonding interface configuration file (<code class="filename">ifcfg-bond0</code> for example). Parameters to bonded interfaces can be configured without unloading (and reloading) the bonding module by manipulating files in the <code class="systemitem">sysfs</code> file system.
+ </div><div class="para">
+ <code class="systemitem">sysfs</code> is a virtual file system that represents kernel objects as directories, files and symbolic links. <code class="systemitem">sysfs</code> can be used to query for information about kernel objects, and can also manipulate those objects through the use of normal file system commands. The <code class="systemitem">sysfs</code> virtual file system is mounted under the <code class="filename">/sys/</code> directory. All bonding interfaces can be configured dynamically by interacting with and manipulating files under the <code class="filename">/sys/class/net/</code> directory.
+ </div><div class="para">
+ In order to determine the best parameters for your bonding interface, create a channel bonding interface file such as <code class="filename">ifcfg-bond0</code> by following the instructions in <a class="xref" href="sec-Create_a_Channel_Bonding_Interface.html">Section 4.3.2, “Create a Channel Bonding Interface”</a>. Insert the <code class="option">SLAVE=yes</code> and <code class="option">MASTER=bond0</code> directives in the configuration files for each interface bonded to <code class="literal">bond0</code>. Once this is completed, you can proceed to testing the parameters.
+ </div><div class="para">
+ First, bring up the bond you created by running <code class="command">ifup <code class="option">bond<em class="replaceable"><code>N</code></em></code></code> as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">ifup bond0</code></pre><div class="para">
+ If you have correctly created the <code class="filename">ifcfg-bond0</code> bonding interface file, you will be able to see <code class="computeroutput">bond0</code> listed in the output of running <code class="command"> ip link show</code> as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">ip link show</code>
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 1000
+ link/ether 52:54:00:e9:ce:d2 brd ff:ff:ff:ff:ff:ff
+3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP mode DEFAULT qlen 1000
+ link/ether 52:54:00:38:a6:4c brd ff:ff:ff:ff:ff:ff
+4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT
+ link/ether 52:54:00:38:a6:4c brd ff:ff:ff:ff:ff:ff</pre><div class="para">
+ To view all existing bonds, even if they are not up, run:
+ </div><pre class="screen">~]$ <code class="command">cat /sys/class/net/bonding_masters</code>
+bond0</pre><div class="para">
+ You can configure each bond individually by manipulating the files located in the <code class="filename">/sys/class/net/bond<em class="replaceable"><code>N</code></em>/bonding/</code> directory. First, the bond you are configuring must be taken down:
+ </div><pre class="screen">~]# <code class="command">ifdown bond0</code>
+</pre><div class="para">
+ As an example, to enable MII monitoring on bond0 with a 1 second interval, run as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">echo 1000 > /sys/class/net/bond0/bonding/miimon</code>
+</pre><div class="para">
+ To configure bond0 for <em class="parameter"><code>balance-alb</code></em> mode, run either:
+ </div><pre class="screen">~]# <code class="command">echo 6 > /sys/class/net/bond0/bonding/mode</code>
+</pre><div class="para">
+ ...or, using the name of the mode:
+ </div><pre class="screen">~]# <code class="command">echo balance-alb > /sys/class/net/bond0/bonding/mode</code>
+</pre><div class="para">
+ After configuring options for the bond in question, you can bring it up and test it by running <code class="command">ifup bond<em class="replaceable"><code>N</code></em></code>. If you decide to change the options, take the interface down, modify its parameters using <code class="systemitem">sysfs</code>, bring it back up, and re-test.
+ </div><div class="para">
+ Once you have determined the best set of parameters for your bond, add those parameters as a space-separated list to the <em class="parameter"><code>BONDING_OPTS=</code></em> directive of the <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond<em class="replaceable"><code>N</code></em> </code> file for the bonding interface you are configuring. Whenever that bond is brought up (for example, by the system during the boot sequence if the <em class="parameter"><code>ONBOOT=yes</code></em> directive is set), the bonding options specified in the <em class="parameter"><code>BONDING_OPTS</code></em> will take effect for that bond.
+ </div><div class="para">
+ The following list provides the names of many of the more common channel bonding parameters, along with a description of what they do. For more information, see the brief descriptions for each <code class="computeroutput">parm</code> in <code class="command">modinfo bonding</code> output, or for more detailed information, see <a href="https://www.kernel.org/doc/Documentation/networking/bonding.txt">https://www.kernel.org/doc/Documentation/networking/bonding.txt</a>.
+ </div><div class="variablelist"><h6>Bonding Interface Parameters</h6><dl class="variablelist compact"><dt class="varlistentry"><span class="term"> <code class="literal">ad_select=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Specifies the 802.3ad aggregation selection logic to use. Possible values are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>stable</code></strong> or <strong class="userinput"><code>0</code></strong> — Default setting. The active aggregator is chosen by largest aggregate bandwidth. Reselection of the active aggregator occurs only when all slaves of the active aggregator are down or if the active aggregator has no slaves.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>bandwidth</code></strong> or <strong class="userinput"><code>1</code></strong> — The active aggregator is chosen by largest aggregate bandwidth. Reselection occurs if:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ A slave is added to or removed from the bond;
+ </div></li><li class="listitem"><div class="para">
+ Any slave's link state changes;
+ </div></li><li class="listitem"><div class="para">
+ Any slave's 802.3ad association state changes;
+ </div></li><li class="listitem"><div class="para">
+ The bond's administrative state changes to up.
+ </div></li></ul></div>
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>count</code></strong> or <strong class="userinput"><code>2</code></strong> — The active aggregator is chosen by the largest number of slaves. Reselection occurs as described for the <code class="option">bandwidth</code> setting above.
+ </div></li></ul></div>
+ The <code class="option">bandwidth</code> and <code class="option">count</code> selection policies permit failover of 802.3ad aggregations when partial failure of the active aggregator occurs. This keeps the aggregator with the highest availability, either in bandwidth or in number of slaves, active at all times.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">arp_interval=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies, in milliseconds, how often <code class="systemitem">ARP</code> monitoring occurs.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ It is essential that both <code class="literal">arp_interval</code> and <code class="literal">arp_ip_target</code> parameters are specified, or, alternatively, the <code class="literal">miimon</code> parameter is specified. Failure to do so can cause degradation of network performance in the event that a link fails.
+ </div></div></div><div class="para">
+ If using this setting while in <code class="literal">mode=0</code> or <code class="literal">mode=2</code> (the two load-balancing modes), the network switch must be configured to distribute packets evenly across the NICs. For more information on how to accomplish this, see <a href="https://www.kernel.org/doc/Documentation/networking/bonding.txt">https://www.kernel.org/doc/Documentation/networking/bonding.txt</a>.
+ </div><div class="para">
+ The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">arp_ip_target=<em class="replaceable"><code>ip_address</code></em>[<span class="optional">,<em class="replaceable"><code>ip_address_2</code></em>,…<em class="replaceable"><code>ip_address_16</code></em></span>] </code> </span></dt><dd><div class="para">
+ Specifies the target <code class="systemitem">IP</code> address of <code class="systemitem">ARP</code> requests when the <code class="literal">arp_interval</code> parameter is enabled. Up to 16 <code class="systemitem">IP</code> addresses can be specified in a comma separated list.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">arp_validate=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Validate source/distribution of <code class="systemitem">ARP</code> probes; default is <strong class="userinput"><code>none</code></strong>. Other valid values are <strong class="userinput"><code>active</code></strong>, <strong class="userinput"><code>backup</code></strong>, and <strong class="userinput"><code>all</code></strong>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">downdelay=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how long to wait after link failure before disabling the link. The value must be a multiple of the value specified in the <code class="literal">miimon</code> parameter. The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">fail_over_mac=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Specifies whether active-backup mode should set all slaves to the same MAC address at enslavement (the traditional behavior), or, when enabled, perform special handling of the bond's MAC address in accordance with the selected policy. Possible values are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>none</code></strong> or <strong class="userinput"><code>0</code></strong> — Default setting. This setting disables <code class="literal">fail_over_mac</code>, and causes bonding to set all slaves of an active-backup bond to the same MAC address at enslavement time.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>active</code></strong> or <strong class="userinput"><code>1</code></strong> — The <span class="quote">“<span class="quote">active</span>”</span> <code class="literal">fail_over_mac</code> policy indicates that the MAC address of the bond should always be the MAC address of the currently active slave. The MAC address of the slaves is not changed; instead, the MAC address of the bond changes during a failover.
+ </div><div class="para">
+ This policy is useful for devices that cannot ever alter their MAC address, or for devices that refuse incoming broadcasts with their own source MAC (which interferes with the ARP monitor). The disadvantage of this policy is that every device on the network must be updated via gratuitous ARP, as opposed to the normal method of switches snooping incoming traffic to update their ARP tables. If the gratuitous ARP is lost, communication may be disrupted.
+ </div><div class="para">
+ When this policy is used in conjunction with the MII monitor, devices which assert link up prior to being able to actually transmit and receive are particularly susceptible to loss of the gratuitous ARP, and an appropriate updelay setting may be required.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>follow</code></strong> or <strong class="userinput"><code>2</code></strong> — The <span class="quote">“<span class="quote">follow</span>”</span> <code class="literal">fail_over_mac</code> policy causes the MAC address of the bond to be selected normally (normally the MAC address of the first slave added to the bond). However, the second and subsequent slaves are not set to this MAC address while they are in a backup role; a slave is programmed with the bond's MAC address at failover time (and the formerly active slave receives the newly active slave's MAC address).
+ </div><div class="para">
+ This policy is useful for multiport devices that either become confused or incur a performance penalty when multiple ports are programmed with the same MAC address.
+ </div></li></ul></div>
+ </div></dd><dt class="varlistentry"><span class="term">lacp_rate=<em class="replaceable"><code>value</code></em> </span></dt><dd><div class="para">
+ Specifies the rate at which link partners should transmit LACPDU packets in 802.3ad mode. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>slow</code></strong> or <strong class="userinput"><code>0</code></strong> — Default setting. This specifies that partners should transmit LACPDUs every 30 seconds.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>fast</code></strong> or <strong class="userinput"><code>1</code></strong> — Specifies that partners should transmit LACPDUs every 1 second.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">miimon=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how often MII link monitoring occurs. This is useful if high availability is required because MII is used to verify that the NIC is active. To verify that the driver for a particular NIC supports the MII tool, type the following command as root:
+ </div><pre class="screen">~]# <code class="command">ethtool <em class="replaceable"><code>interface_name</code></em> | grep "Link detected:"</code>
+</pre><div class="para">
+ In this command, replace <em class="replaceable"><code>interface_name</code></em>> with the name of the device interface, such as <strong class="userinput"><code>eth0</code></strong>, not the bond interface. If MII is supported, the command returns:
+ </div><pre class="screen">Link detected: yes</pre><div class="para">
+ If using a bonded interface for high availability, the module for each NIC must support MII. Setting the value to <strong class="userinput"><code>0</code></strong> (the default), turns this feature off. When configuring this setting, a good starting point for this parameter is <strong class="userinput"><code>100</code></strong>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ It is essential that both <code class="literal">arp_interval</code> and <code class="literal">arp_ip_target</code> parameters are specified, or, alternatively, the <code class="literal">miimon</code> parameter is specified. Failure to do so can cause degradation of network performance in the event that a link fails.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">mode=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Allows you to specify the bonding policy. The <em class="replaceable"><code>value</code></em> can be one of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-rr</code></strong> or <strong class="userinput"><code>0</code></strong> — Sets a round-robin policy for fault tolerance and load balancing. Transmissions are received and sent out sequentially on each bonded slave interface beginning with the first one available.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>active-backup</code></strong> or <strong class="userinput"><code>1</code></strong> — Sets an active-backup policy for fault tolerance. Transmissions are received and sent out via the first available bonded slave interface. Another bonded slave interface is only used if the active bonded slave interface fails.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-xor</code></strong> or <strong class="userinput"><code>2</code></strong> — Transmissions are based on the selected hash policy. The default is to derive a hash by XOR of the source and destination MAC addresses multiplied by the modulo of the number of slave interfaces. In this mode traffic destined for specific peers will always be sent over the same interface. As the destination is determined by the MAC addresses this method works best for traffic to peers on the same link or local network. If traffic has to pass through a single router then this mode of traffic balancing will be suboptimal.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>broadcast</code></strong> or <strong class="userinput"><code>3</code></strong> — Sets a broadcast policy for fault tolerance. All transmissions are sent on all slave interfaces.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>802.3ad</code></strong> or <strong class="userinput"><code>4</code></strong> — Sets an IEEE 802.3ad dynamic link aggregation policy. Creates aggregation groups that share the same speed and duplex settings. Transmits and receives on all slaves in the active aggregator. Requires a switch that is 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-tlb</code></strong> or <strong class="userinput"><code>5</code></strong> — Sets a Transmit Load Balancing (TLB) policy for fault tolerance and load balancing. The outgoing traffic is distributed according to the current load on each slave interface. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed slave. This mode is only suitable for local addresses known to the kernel bonding module and therefore cannot be used behind a bridge with virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-alb</code></strong> or <strong class="userinput"><code>6</code></strong> — Sets an Adaptive Load Balancing (ALB) policy for fault tolerance and load balancing. Includes transmit and receive load balancing for <code class="systemitem">IPv4</code> traffic. Receive load balancing is achieved through <code class="systemitem">ARP</code> negotiation. This mode is only suitable for local addresses known to the kernel bonding module and therefore cannot be used behind a bridge with virtual machines.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">primary=<em class="replaceable"><code>interface_name</code></em> </code> </span></dt><dd><div class="para">
+ Specifies the interface name, such as <strong class="userinput"><code>eth0</code></strong>, of the primary device. The <code class="literal">primary</code> device is the first of the bonding interfaces to be used and is not abandoned unless it fails. This setting is particularly useful when one NIC in the bonding interface is faster and, therefore, able to handle a bigger load.
+ </div><div class="para">
+ This setting is only valid when the bonding interface is in <strong class="userinput"><code>active-backup</code></strong> mode. See <a href="https://www.kernel.org/doc/Documentation/networking/bonding.txt">https://www.kernel.org/doc/Documentation/networking/bonding.txt</a> for more information.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">primary_reselect=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Specifies the reselection policy for the primary slave. This affects how the primary slave is chosen to become the active slave when failure of the active slave or recovery of the primary slave occurs. This parameter is designed to prevent flip-flopping between the primary slave and other slaves. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>always</code></strong> or <strong class="userinput"><code>0</code></strong> (default) — The primary slave becomes the active slave whenever it comes back up.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>better</code></strong> or <strong class="userinput"><code>1</code></strong> — The primary slave becomes the active slave when it comes back up, if the speed and duplex of the primary slave is better than the speed and duplex of the current active slave.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>failure</code></strong> or <strong class="userinput"><code>2</code></strong> — The primary slave becomes the active slave only if the current active slave fails and the primary slave is up.
+ </div></li></ul></div><div class="para">
+ The <code class="literal">primary_reselect</code> setting is ignored in two cases:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If no slaves are active, the first slave to recover is made the active slave.
+ </div></li><li class="listitem"><div class="para">
+ When initially enslaved, the primary slave is always made the active slave.
+ </div></li></ul></div><div class="para">
+ Changing the <code class="literal">primary_reselect</code> policy via <code class="systemitem">sysfs</code> will cause an immediate selection of the best active slave according to the new policy. This may or may not result in a change of the active slave, depending upon the circumstances
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">resend_igmp=<em class="replaceable"><code>range</code></em></code></span></dt><dd><div class="para">
+ Specifies the number of IGMP membership reports to be issued after a failover event. One membership report is issued immediately after the failover, subsequent packets are sent in each 200ms interval.
+ </div><div class="para">
+ The valid range is <code class="literal">0</code> to <code class="literal">255</code>; the default value is <code class="literal">1</code>. A value of <code class="literal">0</code> prevents the IGMP membership report from being issued in response to the failover event.
+ </div><div class="para">
+ This option is useful for bonding modes <code class="command">balance-rr</code> (mode 0), <code class="command">active-backup</code> (mode 1), <code class="command">balance-tlb</code> (mode 5) and <code class="command">balance-alb</code> (mode 6), in which a failover can switch the IGMP traffic from one slave to another. Therefore a fresh IGMP report must be issued to cause the switch to forward the incoming IGMP traffic over the newly selected slave.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">updelay=<em class="replaceable"><code>time_in_milliseconds</code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how long to wait before enabling a link. The value must be a multiple of the value specified in the <code class="literal">miimon</code> parameter. The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">use_carrier=<em class="replaceable"><code>number</code></em> </code> </span></dt><dd><div class="para">
+ Specifies whether or not <code class="literal">miimon</code> should use MII/ETHTOOL ioctls or <code class="function">netif_carrier_ok()</code> to determine the link state. The <code class="function">netif_carrier_ok()</code> function relies on the device driver to maintains its state with <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em></code>; most device drivers support this function.
+ </div><div class="para">
+ The MII/ETHTOOL ioctls tools utilize a deprecated calling sequence within the kernel. However, this is still configurable in case your device driver does not support <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em></code>.
+ </div><div class="para">
+ Valid values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> — Default setting. Enables the use of <code class="function">netif_carrier_ok()</code>.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> — Enables the use of MII/ETHTOOL ioctls.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If the bonding interface insists that the link is up when it should not be, it is possible that your network device driver does not support <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em></code>.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">xmit_hash_policy=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Selects the transmit hash policy used for slave selection in <strong class="userinput"><code>balance-xor</code></strong> and <strong class="userinput"><code>802.3ad</code></strong> modes. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> or <strong class="userinput"><code>layer2</code></strong> — Default setting. This parameter uses the XOR of hardware MAC addresses to generate the hash. The formula used is:
+ </div><pre class="screen">(<em class="replaceable"><code>source_MAC_address</code></em> XOR <em class="replaceable"><code>destination_MAC</code></em>) MODULO <em class="replaceable"><code>slave_count</code></em>
+</pre><div class="para">
+ This algorithm will place all traffic to a particular network peer on the same slave, and is 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> or <strong class="userinput"><code>layer3+4</code></strong> — Uses upper layer protocol information (when available) to generate the hash. This allows for traffic to a particular network peer to span multiple slaves, although a single connection will not span multiple slaves.
+ </div><div class="para">
+ The formula for unfragmented TCP and UDP packets used is:
+ </div><pre class="screen">((<em class="replaceable"><code>source_port</code></em> XOR <em class="replaceable"><code>dest_port</code></em>) XOR
+ ((<em class="replaceable"><code>source_IP</code></em> XOR <em class="replaceable"><code>dest_IP</code></em>) AND <code class="constant">0xffff</code>)
+ MODULO <em class="replaceable"><code>slave_count</code></em>
+</pre><div class="para">
+ For fragmented TCP or UDP packets and all other <code class="systemitem">IP</code> protocol traffic, the source and destination port information is omitted. For non-<code class="systemitem">IP</code> traffic, the formula is the same as the <code class="command">layer2</code> transmit hash policy.
+ </div><div class="para">
+ This policy intends to mimic the behavior of certain switches; particularly, Cisco switches with PFC2 as well as some Foundry and IBM products.
+ </div><div class="para">
+ The algorithm used by this policy is not 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>2</code></strong> or <strong class="userinput"><code>layer2+3</code></strong> — Uses a combination of layer2 and layer3 protocol information to generate the hash.
+ </div><div class="para">
+ Uses XOR of hardware MAC addresses and <code class="systemitem">IP</code> addresses to generate the hash. The formula is:
+ </div><pre class="screen">(((<em class="replaceable"><code>source_IP</code></em> XOR <em class="replaceable"><code>dest_IP</code></em>) AND <code class="constant">0xffff</code>) XOR
+ ( <em class="replaceable"><code>source_MAC</code></em> XOR <em class="replaceable"><code>destination_MAC</code></em> ))
+ MODULO <em class="replaceable"><code>slave_count</code></em>
+</pre><div class="para">
+ This algorithm will place all traffic to a particular network peer on the same slave. For non-<code class="systemitem">IP</code> traffic, the formula is the same as for the layer2 transmit hash policy.
+ </div><div class="para">
+ This policy is intended to provide a more balanced distribution of traffic than layer2 alone, especially in environments where a layer3 gateway device is required to reach most destinations.
+ </div><div class="para">
+ This algorithm is 802.3ad compliant.
+ </div></li></ul></div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Creating_Multiple_Bonds.html"><strong>Prev</strong>4.3.5. Creating Multiple Bonds</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Network_Bonding_Using_the_NetworkManager_Command_Line_Tool_nmcli.html"><strong>Next</strong>4.5. Using the NetworkManager Command Line Tool, ...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html
new file mode 100644
index 0000000..5cbb67c
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2. Using NetworkManager with the GNOME Graphical User Interface</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Networking.html" title="Chapter 2. Configure Networking" /><link rel="prev" href="ch-Configure_Networking.html" title="Chapter 2. Configure Networking" /><link rel="next" href="sec-Configuring_New_and_Editing_Existing_Connections.html" title="2.2.2. Configuring New and Editing Existing Connections" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch
-Configure_Networking.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_New_and_Editing_Existing_Connections.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Using_NetworkManager_with_the_GNOME_Graphical_User_Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Using NetworkManager with the GNOME Graphical User Interface</h2></div></div></div><div class="para">
+ As of <span class="application"><strong>Fedora 20</strong></span>, <span class="application"><strong>NetworkManager</strong></span>'s own graphical user interface (GUI) is not used by default. The <span class="guilabel"><strong>Network</strong></span> settings configuration tool is provided as part of the new GNOME <span class="application"><strong>control-center</strong></span> GUI. The old <span class="application"><strong>nm-connection-editor</strong></span> GUI is still available for certain tasks.
+ </div><div class="section" id="sec-Connecting_to_a_Network_Using_a_GUI"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.1. Connecting to a Network Using a GUI</h3></div></div></div><div class="para">
+ Access the <span class="guilabel"><strong>Network</strong></span> settings window of the <span class="application"><strong>control-center</strong></span> application as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">control network</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="guilabel"><strong>Network</strong></span> settings tool appears. Proceed to <a class="xref" href="sec-Configuring_New_and_Editing_Existing_Connections.html">Section 2.2.2, “Configuring New and Editing Existing Connections”</a>
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Configure_Networking.html"><strong>Prev</strong>Chapter 2. Configure Networking</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_New_and_Editing_Existing_Connections.html"><strong>Next</strong>2.2.2. Configuring New and Editing Existing Conne...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Using_the_Command_Line_Interface.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Using_the_Command_Line_Interface.html
new file mode 100644
index 0000000..f381303
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Using_the_Command_Line_Interface.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3. Using the Command Line Interface (CLI)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Networking.html" title="Chapter 2. Configure Networking" /><link rel="prev" href="sec-Configuring_Connection_Settings.html" title="2.2.10. Configuring Connection Settings" /><link rel="next" href="sec-Configuring_a_Network_Interface_Using_ip_commands.html" title="2.3.2. Configuring a Network Interface Using ip Commands" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a a
ccesskey="p" href="sec-Configuring_Connection_Settings.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_a_Network_Interface_Using_ip_commands.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Using_the_Command_Line_Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.3. Using the Command Line Interface (CLI)</h2></div></div></div><div class="section" id="sec-Configuring_a_Network_Interface_Using_ifcg_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.1. Configuring a Network Interface Using ifcfg Files</h3></div></div></div><div class="para">
+ Interface configuration files control the software interfaces for individual network devices. As the system boots, it uses these files to determine what interfaces to bring up and how to configure them. These files are usually named <code class="filename">ifcfg-<em class="replaceable"><code>name</code></em></code>, where the suffix <em class="replaceable"><code>name</code></em> refers to the name of the device that the configuration file controls. By convention, the <code class="filename">ifcfg</code> file's suffix is the same as the string given by the <code class="command">DEVICE</code> directive in the configuration file itself.
+ </div><h4 id="bh-Static_Network_Settings">Static Network Settings</h4><div class="para">
+ To configure an interface with static network settings using <code class="filename">ifcfg</code> files, for an interface with the name <span class="interface">eth0</span>, create a file with name <code class="filename">ifcfg-eth0</code> in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory as follows:
+<pre class="programlisting">DEVICE=eth0
+BOOTPROTO=none
+ONBOOT=yes
+PREFIX=24
+IPADDR=10.0.1.27
+</pre>
+ Optionally specify the hardware or MAC address using the <code class="command">HWADDR</code> directive. Note that this may influence the device naming procedure as explained in <a class="xref" href="ch-Consistent_Network_Device_Naming.html">Chapter 8, <em>Consistent Network Device Naming</em></a>. You do not need to specify the network or broadcast address as this is calculated automatically by <span class="application"><strong>ipcalc</strong></span>.
+ </div><h4 id="bh-Dynamic_Network_Settings">Dynamic Network Settings</h4><div class="para">
+ To configure an interface with dynamic network settings using <code class="filename">ifcfg</code> files, for an interface with name <span class="interface">em1</span>, create a file with name <code class="filename">ifcfg-em1</code> in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory as follows:
+<pre class="programlisting">DEVICE=em1
+BOOTPROTO=dhcp
+ONBOOT=yes
+</pre>
+ Optionally specify the hardware or MAC address using the <code class="command">HWADDR</code> directive. Note that this may influence the device naming procedure as explained in <a class="xref" href="ch-Consistent_Network_Device_Naming.html">Chapter 8, <em>Consistent Network Device Naming</em></a>. You do not need to specify the network or broadcast address as this is calculated automatically by <span class="application"><strong>ipcalc</strong></span>.
+ </div><div class="para">
+ To configure an interface to send a different host name to the <code class="systemitem">DHCP</code> server, add the following line to the <code class="filename">ifcfg</code> file. <pre class="synopsis">DHCP_HOSTNAME=<em class="replaceable"><code>hostname</code></em></pre>
+ </div><div class="para">
+ To configure an interface to ignore routes sent by a <code class="systemitem">DHCP</code> server, add the following line to the <code class="filename">ifcfg</code> file. <pre class="synopsis">PEERDNS=no</pre> This will prevent network service from updating <code class="filename">/etc/resolv.conf</code> with the <code class="systemitem">DNS</code> servers received from a <code class="systemitem">DHCP</code> server.
+ </div><div class="para">
+ To configure an interface to use particular <code class="systemitem">DNS</code> servers, set <code class="command">PEERDNS=no</code> as described above and add lines as follows to the <code class="filename">ifcfg</code> file:
+<pre class="programlisting">DNS1=<em class="replaceable"><code>ip-address</code></em>
+DNS2=<em class="replaceable"><code>ip-address</code></em></pre>
+ where <em class="replaceable"><code>ip-address</code></em> is the address of a <code class="systemitem">DNS</code> server. This will cause the network service to update <code class="filename">/etc/resolv.conf</code> with the <code class="systemitem">DNS</code> servers specified.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> will by default call the <code class="systemitem">DHCP</code> client, <span class="application"><strong>dhclient</strong></span>, when a profile has been set to obtain addresses automatically, or when an interface configuration file has BOOTPROTO set to <code class="literal">dhcp</code>. Where <code class="systemitem">DHCP</code> is required, an instance of <code class="systemitem">dhclient</code> is started for every Internet protocol, <code class="systemitem">IPv4</code> and <code class="systemitem">IPv6</code>, on an interface. Where <span class="application"><strong>NetworkManager</strong></span> is not running, or not managing an interface, then the legacy network service will call instances of <code class="systemitem">dhclient</code> as required.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Connection_Settings.html"><strong>Prev</strong>2.2.10. Configuring Connection Settings</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_a_Network_Interface_Using_ip_commands.html"><strong>Next</strong>2.3.2. Configuring a Network Interface Using ip C...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html
new file mode 100644
index 0000000..2153f92
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Using_the_NetworkManager_Command_Line_Tool_nmcli.html
@@ -0,0 +1,86 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4. Using the NetworkManager Command Line Tool, nmcli</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Networking.html" title="Chapter 2. Configure Networking" /><link rel="prev" href="sec-Configuring_IPv6_Tokenized_Interface_Identifiers.html" title="2.3.5. Configuring IPv6 Tokenized Interface Identifiers" /><link rel="next" href="sec-Connecting_to_a_Network_Using_nmcli.html" title="2.4.2. Connecting to a Network Using nmcli" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"
><a accesskey="p" href="sec-Configuring_IPv6_Tokenized_Interface_Identifiers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Connecting_to_a_Network_Using_nmcli.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Using_the_NetworkManager_Command_Line_Tool_nmcli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.4. Using the NetworkManager Command Line Tool, nmcli</h2></div></div></div><div class="para">
+ The command‐line tool <span class="application"><strong>nmcli</strong></span> can be used by both users and scripts for controlling <span class="application"><strong>NetworkManager</strong></span>. The basic format of a command is as follows: <pre class="synopsis">nmcli <code class="option">OPTIONS</code> OBJECT { <code class="command">COMMAND</code> | help }</pre> where OBJECT can be one of <code class="literal">general</code>, <code class="literal">networking</code>, <code class="literal">radio</code>, <code class="literal">connection</code>, or <code class="literal">device</code>. The most used options are: <code class="option">-t, --terse</code> for use in scripts, the <code class="option">-p, --pretty</code> option for users, and the <code class="option">-h, --help</code> option. Command completion has been implemented for <span class="application"><strong>nmcli</strong></span>, so remember to press <span class="keycap"><strong>Tab</strong></span> whenever you are
unsure of the command options available. See the <code class="filename">nmcli(1)</code> man page for a complete list of the options and commands.
+ </div><div class="para">
+ The <span class="application"><strong>nmcli</strong></span> tool has some built-in context-sensitive help. For example, issue the following two commands and notice the difference:
+<pre class="screen">~]$ <code class="command">nmcli help</code>
+Usage: nmcli [OPTIONS] OBJECT { COMMAND | help }
+
+OPTIONS
+ -t[erse] terse output
+ -p[retty] pretty output
+ -m[ode] tabular|multiline output mode
+ -f[ields] <field1,field2,...>|all|common specify fields to output
+ -e[scape] yes|no escape columns separators in values
+ -n[ocheck] don't check nmcli and NetworkManager versions
+ -a[sk] ask for missing parameters
+ -w[ait] <seconds> set timeout waiting for finishing operations
+ -v[ersion] show program version
+ -h[elp] print this help
+
+OBJECT
+ g[eneral] NetworkManager's general status and operations
+ n[etworking] overall networking control
+ r[adio] NetworkManager radio switches
+ c[onnection] NetworkManager's connections
+ d[evice] devices managed by NetworkManager</pre>
+
+<pre class="screen">~]$ <code class="command">nmcli general help</code>
+Usage: nmcli general { COMMAND | help }
+
+ COMMAND := { status | hostname | permissions | logging }
+
+ status
+
+ hostname [<hostname>]
+
+ permissions
+
+ logging [level <log level>] [domains <log domains>]</pre>
+ In the second example above the help is related to the object <code class="literal">general</code>.
+ </div><div class="para">
+ The <code class="filename">nmcli-examples(5)</code> man page has many useful examples. A brief selection is shown here:
+ </div><div class="para">
+ To show the overall status of <span class="application"><strong>NetworkManager</strong></span>: <pre class="synopsis">nmcli general status</pre> To control <span class="application"><strong>NetworkManager</strong></span> logging: <pre class="synopsis">nmcli general logging</pre> To show all connections: <pre class="synopsis">nmcli connection show</pre> To show only currently active connections, add the <code class="option">-a, --active</code> option as follows: <pre class="synopsis">nmcli connection show --active</pre> To show devices recognized by <span class="application"><strong>NetworkManager</strong></span> and their state: <pre class="synopsis">nmcli device status</pre>
+ </div><div class="para">
+ Commands can be shortened and some options omitted. For example the command: <pre class="synopsis">nmcli connection modify id '<em class="replaceable"><code>MyCafe</code></em>' 802-11-wireless.mtu 1350</pre> Can be reduced to the following command: <pre class="synopsis">nmcli con mod <em class="replaceable"><code>MyCafe</code></em> 802-11-wireless.mtu 1350</pre> The <code class="option">id</code> option can been omitted because the connection ID (name) is unambiguous for <span class="application"><strong>nmcli</strong></span> in this case. As you become familiar with the commands, further abbreviations can be made. For example: <pre class="synopsis">nmcli connection add type ethernet</pre> can be reduced to: <pre class="synopsis">nmcli c a type eth</pre> <div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Remember to use tab completion when in doubt.
+ </div></div></div>
+ </div><h3 id="bh-Starting_and_Stopping_an_Interface_Using_nmcli">Starting and Stopping an Interface Using nmcli</h3><div class="para">
+ The <span class="application"><strong>nmcli</strong></span> tool can be used to start and stop any network interface, including masters. For example:
+<pre class="screen">nmcli con up id bond0
+nmcli con up id port0
+nmcli dev disconnect iface bond0
+nmcli dev disconnect iface eth0</pre>
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ It is recommended to use <code class="command">nmcli dev disconnect iface <em class="replaceable"><code>iface-name</code></em></code> rather than <code class="command">nmcli con down id <em class="replaceable"><code>id-string</code></em></code> because disconnection places the interface into a <span class="quote">“<span class="quote">manual</span>”</span> mode, in which no automatic connection will be started until the user tells <span class="application"><strong>NetworkManager</strong></span> to start a connection or until an external event like a carrier change, hibernate, or sleep, occurs.
+ </div></div></div><h3 id="bh-The_nmcli_Interactive_Connection_Editor">The nmcli Interactive Connection Editor</h3><div class="para">
+ The <span class="application"><strong>nmcli</strong></span> tool has an interactive connection editor. To use it, enter the following command:
+<pre class="screen">~]$ <code class="command">nmcli con edit</code></pre>
+ You will be prompted to enter a valid connection type from the list displayed. After entering a connection type you will be placed at the <span class="application"><strong>nmcli</strong></span> prompt. If you are familiar with the connection types you can add a valid connection <code class="option">type</code> option to the <code class="command">nmcli con edit</code> command and be taken straight to the <span class="application"><strong>nmcli</strong></span> prompt. The format is as follows for editing an existing connection profile: <pre class="synopsis">nmcli con edit [id | uuid | path] <em class="replaceable"><code>ID</code></em></pre> For adding and editing a new connection profile, the following format applies: <pre class="synopsis">nmcli con edit [type <em class="replaceable"><code>new-connection-type</code></em>] [con-name <em class="replaceable"><code>new-connection-name</code></em>]</pre>
+ </div><div class="para">
+ Type <code class="command">help</code> at the <span class="application"><strong>nmcli</strong></span> prompt to see a list of valid commands. Use the <code class="command">describe</code> command to get a description of settings and their properties. The format is as follows: <pre class="synopsis">describe <em class="replaceable"><code>setting.property</code></em></pre> For example:
+<pre class="screen">nmcli> <code class="command">describe team.config</code></pre>
+
+ </div><div class="section" id="sec-Understanding_the_nmcli_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.1. Understanding the nmcli Options</h3></div></div></div><div class="para">
+ Many of the <span class="application"><strong>nmcli</strong></span> commands are self-explanatory, however a few command options are worth a moments study:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="option">type</code> — The connection type.</span></dt><dd><div class="para">
+ Allowed values are: <code class="literal">adsl</code>, <code class="literal">bond</code>, <code class="literal">bond-slave</code>, <code class="literal">bridge</code>, <code class="literal">bridge-slave</code>, <code class="literal">bluetooth</code>, <code class="literal">cdma</code>, <code class="literal">ethernet</code>, <code class="literal">gsm</code>, <code class="literal">infiniband</code>, <code class="literal">olpc-mesh</code>, <code class="literal">team</code>, <code class="literal">team-slave</code>, <code class="literal">vlan</code>, <code class="literal">wifi</code>, <code class="literal">wimax</code>.
+ </div><div class="para">
+ Each connection type has type-specific command options. Press <span class="keycap"><strong>Tab</strong></span> to see a list of them or see the <code class="literal">TYPE_SPECIFIC_OPTIONS</code> list in the <code class="filename">nmcli(1)</code> man page. The <code class="option">type</code> option is applicable after the following: <code class="command">nmcli connection add</code> and <code class="command">nmcli connection edit</code>.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">con-name</code> — The name assigned to a connection profile.</span></dt><dd><div class="para">
+ If you do not specify a connection name, one will be generated as follows: <pre class="synopsis"> <code class="literal">type</code>-ifname[-number]</pre>
+ </div><div class="para">
+ The connection name is the name of a <em class="firstterm">connection profile</em> and should not be confused with the interface name that denotes a device (<span class="interface">wlan0</span>, <span class="interface">eth0</span>, <span class="interface">em1</span>, and so on). Users can however name the connections after interfaces, but they are not the same thing. There can be multiple connection profiles available for a device. This is particularly useful for mobile devices or when switching a network cable back and forth between different devices. Rather than edit the configuration, create different profiles and apply them to the interface as needed. The <code class="option">id</code> option also refers to the connection profile name.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">id</code> — An identification string assigned by the user to a connection profile.</span></dt><dd><div class="para">
+ The ID can be used in <code class="command">nmcli connection</code> commands to identify a connection. The NAME field in the output always denotes the connection ID (name). It refers to the same connection profile name that the <code class="command">con-name</code> does.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="option">uuid</code> — A unique identification string assigned by the system to a connection profile.</span></dt><dd><div class="para">
+ The UUID can be used in <code class="command">nmcli connection</code> commands to identify a connection.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_IPv6_Tokenized_Interface_Identifiers.html"><strong>Prev</strong>2.3.5. Configuring IPv6 Tokenized Interface Ident...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Connecting_to_a_Network_Using_nmcli.html"><strong>Next</strong>2.4.2. Connecting to a Network Using nmcli</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-View_the_Configuration_of_a_Port_in_a_Network_Team.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-View_the_Configuration_of_a_Port_in_a_Network_Team.html
new file mode 100644
index 0000000..daac05a
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-View_the_Configuration_of_a_Port_in_a_Network_Team.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.11.4. View the Configuration of a Port in a Network Team</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Controlling_teamd_with_teamdctl.html" title="5.11. Controlling teamd with teamdctl" /><link rel="prev" href="sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team.html" title="5.11.3. Apply a Configuration to a Port in a Network Team" /><link rel="next" href="sec-Configure_teamd_Runners.html" title="5.12. Configure teamd Runners" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a a
ccesskey="p" href="sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_teamd_Runners.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-View_the_Configuration_of_a_Port_in_a_Network_Team"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.11.4. View the Configuration of a Port in a Network Team</h3></div></div></div><div class="para">
+ To copy the configuration of a port <span class="interface">em1</span> in a network team <span class="interface">team0</span>, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamdctl team0 port config dump em1</code></pre>
+ This will dump the JSON format configuration of the port to standard output.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Apply_a_Configuration_to_a_Port_in_a_Network_Team.html"><strong>Prev</strong>5.11.3. Apply a Configuration to a Port in a Netw...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configure_teamd_Runners.html"><strong>Next</strong>5.12. Configure teamd Runners</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl.html
new file mode 100644
index 0000000..2615037
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.8. Viewing the Active Port Options of a Team Using teamnl</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Configure_a_Network_Team_Using-the_Command_Line.html" title="5.10. Configure a Network Team Using the Command Line" /><link rel="prev" href="sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils.html" title="5.10.7. Bring up an Interface to a Network Team Using iputils" /><link rel="next" href="sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl.html" title="5.10.9. Setting the Active Port Options of a Team Using teamnl" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images
/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Viewing_the_Active_Ports_of_a_Team_Using_teamnl"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.8. Viewing the Active Port Options of a Team Using teamnl</h3></div></div></div><div class="para">
+ To view or list the <code class="option">activeport</code> option in a network team, using the <span class="application"><strong>teamnl</strong></span> utility, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">teamnl team0 getoption activeport</code>
+0</pre>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Bring_Up_an_interface_to_a_Network_Team_Using_iputils.html"><strong>Prev</strong>5.10.7. Bring up an Interface to a Network Team U...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Setting_the_Active_Ports_of_a_Team_Using_teamnl.html"><strong>Next</strong>5.10.9. Setting the Active Port Options of a Team...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Whats-New.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Whats-New.html
new file mode 100644
index 0000000..1f6dab8d
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-Whats-New.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3. What's new in Fedora 20</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="pr01.html" title="Preface" /><link rel="prev" href="sec-Preface-About_this_book.html" title="2. About This Book" /><link rel="next" href="sec-Preface-Book_Organization.html" title="4. How to Read this Book" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Preface-About_this_book.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Pre
face-Book_Organization.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Whats-New"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3. What's new in Fedora 20</h2></div></div></div><div class="para">
+ <em class="firstterm">Network Teaming</em> has been introduced as an alternative to bonding for link aggregation. It is designed to be easy to maintain, debug and extend. For the user it offers performance and flexibility improvements and should be evaluated for all new installations.
+ </div><div class="para">
+ A new command-line tool, <span class="application"><strong>nmcli</strong></span>, has been introduced to allow users and scripts to interact with <span class="application"><strong>NetworkManager</strong></span>. A simple curses-based user interface for <span class="application"><strong>NetworkManager</strong></span>, <code class="command">nmtui</code>, is also available.
+ </div><div class="para">
+ A number of improvements have been made to <span class="application"><strong>NetworkManager</strong></span> to make it more suitable for use in server applications. In particular, <span class="application"><strong>NetworkManager</strong></span> no longer watches for configuration file changes by default, such as those made by editors or deployment tools. It allows administrators to make it aware of external changes through the <code class="command">nmcli connection reload</code> command. Changes made through <span class="application"><strong>NetworkManager</strong></span>'s D-Bus API or with <span class="application"><strong>nmcli</strong></span> are still effective immediately.
+ </div><div class="para">
+ Not included in this guide, but of interest to network administrators, is the new <em class="firstterm">Open Linux Management Infrastructure</em> or <span class="application"><strong>OpenLMI</strong></span> project. This is an implementation of open industry standards for remote system management, which includes an agent for networking. See the <em class="citetitle">Fedora 20 System Administrator's Guide</em> for information on the OpenLMI Networking Provider.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Preface-About_this_book.html"><strong>Prev</strong>2. About This Book</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Preface-Book_Organization.html"><strong>Next</strong>4. How to Read this Book</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-additional_resources.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-additional_resources.html
new file mode 100644
index 0000000..2e0e913
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-additional_resources.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.4. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Host_Names.html" title="Chapter 3. Configure Host Names" /><link rel="prev" href="sec-Configuring_Host_Names_Using_nmcli.html" title="3.3. Configuring Host Names Using nmcli" /><link rel="next" href="sec-hostnamectl-Online_Documentation.html" title="3.4.2. Online Documentation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Host_Nam
es_Using_nmcli.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-hostnamectl-Online_Documentation.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.4. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding <span class="application"><strong>hostnamectl</strong></span>.
+ </div><div class="section" id="sec-hostnamectl-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.4.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">hostnamectl(1)</code> man page — Describes <span class="application"><strong>hostnamectl</strong></span> including the commands and command options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">hostname(1)</code> man page — Contains an explanation of the <code class="command">hostname</code> and <code class="command">domainname</code> commands.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">hostname(5)</code> man page — Contains an explanation of the host name file, its contents, and use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">hostname(7)</code> man page — Contains an explanation of host name resolution.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">machine-info(5)</code> man page — Describes the local machine information file and the environment variables it contains.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">machine-id(5)</code> man page — Describes the local machine ID configuration file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">systemd-hostnamed.service(8)</code> man page — Describes the <code class="systemitem">systemd-hostnamed</code> system service used by <span class="application"><strong>hostnamectl</strong></span>.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Host_Names_Using_nmcli.html"><strong>Prev</strong>3.3. Configuring Host Names Using nmcli</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-hostnamectl-Online_Documentation.html"><strong>Next</strong>3.4.2. Online Documentation</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-additional-resources.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-additional-resources.html
new file mode 100644
index 0000000..97c9d09
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-additional-resources.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.2.8. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-BIND.html" title="10.2. BIND" /><link rel="prev" href="sec-bind-mistakes.html" title="10.2.7. Common Mistakes to Avoid" /><link rel="next" href="app-Revision_History.html" title="Appendix A. Revision History" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-bind-mistakes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="app-Revis
ion_History.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-bind-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.8. Additional Resources</h3></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding BIND.
+ </div><div class="section" id="sec-bind-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.8.1. Installed Documentation</h4></div></div></div><a id="idm225465375824" class="indexterm"></a><div class="para">
+ BIND features a full range of installed documentation covering many different topics, each placed in its own subject directory. For each item below, replace <em class="replaceable"><code>version</code></em> with the version of the <span class="package">bind</span> package installed on the system:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/</code> </span></dt><dd><div class="para">
+ The main directory containing the most recent documentation. The directory contains the <em class="citetitle">BIND 9 Administrator Reference Manual</em> in HTML and PDF formats, which details BIND resource requirements, how to configure different types of nameservers, how to perform load balancing, and other advanced topics.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/sample/etc/</code> </span></dt><dd><div class="para">
+ The directory containing examples of <code class="systemitem">named</code> configuration files.
+ </div></dd></dl></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="filename">rndc(8)</code> </span></dt><dd><div class="para">
+ The manual page for the <code class="command">rndc</code> name server control utility, containing documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">named(8)</code> </span></dt><dd><div class="para">
+ The manual page for the Internet domain name server <code class="systemitem">named</code>, containing documentation on assorted arguments that can be used to control the BIND nameserver daemon.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">lwresd(8)</code> </span></dt><dd><div class="para">
+ The manual page for the lightweight resolver daemon <code class="systemitem">lwresd</code>, containing documentation on the daemon and its usage.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">named.conf(5)</code> </span></dt><dd><div class="para">
+ The manual page with a comprehensive list of options available within the <code class="systemitem">named</code> configuration file.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">rndc.conf(5)</code> </span></dt><dd><div class="para">
+ The manual page with a comprehensive list of options available within the <code class="command">rndc</code> configuration file.
+ </div></dd></dl></div></div><div class="section" id="sec-bind-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.8.2. Useful Websites</h4></div></div></div><a id="idm225436340208" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a href="http://www.isc.org/software/bind">http://www.isc.org/software/bind</a> </span></dt><dd><div class="para">
+ The home page of the BIND project containing information about current releases as well as a PDF version of the <em class="citetitle">BIND 9 Administrator Reference Manual</em>.
+ </div></dd></dl></div></div><div class="section" id="sec-bind-related-books"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.8.3. Related Books</h4></div></div></div><a id="idm225452746576" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><em class="citetitle">DNS and BIND</em> by Paul Albitz and Cricket Liu; O'Reilly & Associates</span></dt><dd><div class="para">
+ A popular reference that explains both common and esoteric BIND configuration options, and provides strategies for securing a DNS server.
+ </div></dd><dt class="varlistentry"><span class="term"><em class="citetitle">The Concise Guide to DNS and BIND</em> by Nicolai Langfeldt; Que</span></dt><dd><div class="para">
+ Looks at the connection between multiple network services and BIND, with an emphasis on task-oriented, technical topics.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-bind-mistakes.html"><strong>Prev</strong>10.2.7. Common Mistakes to Avoid</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="app-Revision_History.html"><strong>Next</strong>Appendix A. Revision History</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-dig.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-dig.html
new file mode 100644
index 0000000..accd26c
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-dig.html
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.2.5. Using the dig Utility</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-BIND.html" title="10.2. BIND" /><link rel="prev" href="sec-bind-rndc.html" title="10.2.4. Using the rndc Utility" /><link rel="next" href="sec-bind-features.html" title="10.2.6. Advanced Features of BIND" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-bind-rndc.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-bind-features.
html"><strong>Next</strong></a></li></ul><div class="section" id="sec-bind-dig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.5. Using the dig Utility</h3></div></div></div><a id="idm225446506016" class="indexterm"></a><div class="para">
+ The <code class="command">dig</code> utility is a command-line tool that allows you to perform <code class="systemitem">DNS</code> lookups and debug a nameserver configuration. Its typical usage is as follows:
+ </div><pre class="screen"><code class="command">dig</code> [@<em class="replaceable"><code>server</code></em>] [<em class="replaceable"><code>option</code></em>...] <em class="replaceable"><code>name</code></em> <em class="replaceable"><code>type</code></em></pre><div class="para">
+ Refer to <a class="xref" href="sec-bind-zone.html#sec-bind-zone-rr">Section 10.2.3.2, “Common Resource Records”</a> for a list of common values to use for <em class="replaceable"><code>type</code></em>.
+ </div><div class="section" id="sec-bind-dig-ns"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.5.1. Looking Up a Nameserver</h4></div></div></div><div class="para">
+ To look up a nameserver for a particular domain, use the command in the following form:
+ </div><pre class="screen"><code class="command">dig</code> <em class="replaceable"><code>name</code></em> NS</pre><div class="para">
+ In <a class="xref" href="sec-bind-dig.html#example-bind-dig-ns">Example 10.17, “A sample nameserver lookup”</a>, the <code class="command">dig</code> utility is used to display nameservers for <code class="systemitem">example.com</code>.
+ </div><div class="example" id="example-bind-dig-ns"><h6>Example 10.17. A sample nameserver lookup</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig example.com NS</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> example.com NS
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57883
+;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
+
+;; QUESTION SECTION:
+;example.com. IN NS
+
+;; ANSWER SECTION:
+example.com. 99374 IN NS a.iana-servers.net.
+example.com. 99374 IN NS b.iana-servers.net.
+
+;; Query time: 1 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:04:06 2010
+;; MSG SIZE rcvd: 77</pre></div></div><br class="example-break" /></div><div class="section" id="sec-bind-dig-a"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.5.2. Looking Up an IP Address</h4></div></div></div><div class="para">
+ To look up an <code class="systemitem">IP</code> address assigned to a particular domain, use the command in the following form:
+ </div><pre class="screen"><code class="command">dig</code> <em class="replaceable"><code>name</code></em> A</pre><div class="para">
+ In <a class="xref" href="sec-bind-dig.html#example-bind-dig-a">Example 10.18, “A sample IP address lookup”</a>, the <code class="command">dig</code> utility is used to display the <code class="systemitem">IP</code> address of <code class="systemitem">example.com</code>.
+ </div><div class="example" id="example-bind-dig-a"><h6>Example 10.18. A sample IP address lookup</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig example.com A</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> example.com A
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4849
+;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
+
+;; QUESTION SECTION:
+;example.com. IN A
+
+;; ANSWER SECTION:
+example.com. 155606 IN A 192.0.32.10
+
+;; AUTHORITY SECTION:
+example.com. 99175 IN NS a.iana-servers.net.
+example.com. 99175 IN NS b.iana-servers.net.
+
+;; Query time: 1 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:07:25 2010
+;; MSG SIZE rcvd: 93</pre></div></div><br class="example-break" /></div><div class="section" id="sec-bind-dig-x"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.5.3. Looking Up a Host Name</h4></div></div></div><div class="para">
+ To look up a host name for a particular <code class="systemitem">IP</code> address, use the command in the following form:
+ </div><pre class="screen"><code class="command">dig</code> <code class="option">-x</code> <em class="replaceable"><code>address</code></em></pre><div class="para">
+ In <a class="xref" href="sec-bind-dig.html#example-bind-dig-x">Example 10.19, “A Sample Host Name Lookup”</a>, the <code class="command">dig</code> utility is used to display the host name assigned to <code class="systemitem">192.0.32.10</code>.
+ </div><div class="example" id="example-bind-dig-x"><h6>Example 10.19. A Sample Host Name Lookup</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig -x 192.0.32.10</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> -x 192.0.32.10
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29683
+;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 6
+
+;; QUESTION SECTION:
+;10.32.0.192.in-addr.arpa. IN PTR
+
+;; ANSWER SECTION:
+10.32.0.192.in-addr.arpa. 21600 IN PTR www.example.com.
+
+;; AUTHORITY SECTION:
+32.0.192.in-addr.arpa. 21600 IN NS b.iana-servers.org.
+32.0.192.in-addr.arpa. 21600 IN NS c.iana-servers.net.
+32.0.192.in-addr.arpa. 21600 IN NS d.iana-servers.net.
+32.0.192.in-addr.arpa. 21600 IN NS ns.icann.org.
+32.0.192.in-addr.arpa. 21600 IN NS a.iana-servers.net.
+
+;; ADDITIONAL SECTION:
+a.iana-servers.net. 13688 IN A 192.0.34.43
+b.iana-servers.org. 5844 IN A 193.0.0.236
+b.iana-servers.org. 5844 IN AAAA 2001:610:240:2::c100:ec
+c.iana-servers.net. 12173 IN A 139.91.1.10
+c.iana-servers.net. 12173 IN AAAA 2001:648:2c30::1:10
+ns.icann.org. 12884 IN A 192.0.34.126
+
+;; Query time: 156 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:25:15 2010
+;; MSG SIZE rcvd: 310</pre></div></div><br class="example-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-bind-rndc.html"><strong>Prev</strong>10.2.4. Using the rndc Utility</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-bind-features.html"><strong>Next</strong>10.2.6. Advanced Features of BIND</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-features.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-features.html
new file mode 100644
index 0000000..4229ce8
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-features.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.2.6. Advanced Features of BIND</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-BIND.html" title="10.2. BIND" /><link rel="prev" href="sec-bind-dig.html" title="10.2.5. Using the dig Utility" /><link rel="next" href="sec-bind-mistakes.html" title="10.2.7. Common Mistakes to Avoid" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-bind-dig.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-bind-mistakes.html
"><strong>Next</strong></a></li></ul><div class="section" id="sec-bind-features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.6. Advanced Features of BIND</h3></div></div></div><div class="para">
+ Most BIND implementations only use the <code class="systemitem">named</code> service to provide name resolution services or to act as an authority for a particular domain. However, BIND version 9 has a number of advanced features that allow for a more secure and efficient <code class="systemitem">DNS</code> service.
+ </div><div class="important"><div class="admonition_header"><h2>Make sure the feature is supported</h2></div><div class="admonition"><div class="para">
+ Before attempting to use advanced features like DNSSEC, TSIG, or IXFR (Incremental Zone Transfer), make sure that the particular feature is supported by all nameservers in the network environment, especially when you use older versions of BIND or non-BIND servers.
+ </div></div></div><div class="para">
+ All of the features mentioned are discussed in greater detail in the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="sec-bind-additional-resources.html#sec-bind-installed-docs">Section 10.2.8.1, “Installed Documentation”</a>.
+ </div><div class="section" id="sec-bind-features-views"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.6.1. Multiple Views</h4></div></div></div><a id="idm225485840320" class="indexterm"></a><div class="para">
+ Optionally, different information can be presented to a client depending on the network a request originates from. This is primarily used to deny sensitive <code class="systemitem">DNS</code> entries from clients outside of the local network, while allowing queries from clients inside the local network.
+ </div><div class="para">
+ To configure multiple views, add the <code class="command">view</code> statement to the <code class="filename">/etc/named.conf</code> configuration file. Use the <code class="option">match-clients</code> option to match <code class="systemitem">IP</code> addresses or entire networks and give them special options and zone data.
+ </div></div><div class="section" id="sec-bind-features-ixfr"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.6.2. Incremental Zone Transfers (IXFR)</h4></div></div></div><a id="idm225441177440" class="indexterm"></a><div class="para">
+ <em class="firstterm">Incremental Zone Transfers</em> (<em class="firstterm">IXFR</em>) allow a secondary nameserver to only download the updated portions of a zone modified on a primary nameserver. Compared to the standard transfer process, this makes the notification and update process much more efficient.
+ </div><a id="idm225440091360" class="indexterm"></a><div class="para">
+ Note that IXFR is only available when using dynamic updating to make changes to master zone records. If manually editing zone files to make changes, <em class="firstterm">Automatic Zone Transfer</em> (<em class="firstterm">AXFR</em>) is used.
+ </div></div><div class="section" id="sec-bind-features-tsig"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.6.3. Transaction SIGnatures (TSIG)</h4></div></div></div><a id="idm225449460000" class="indexterm"></a><div class="para">
+ <em class="firstterm">Transaction SIGnatures</em> (TSIG) ensure that a shared secret key exists on both primary and secondary nameservers before allowing a transfer. This strengthens the standard <code class="systemitem">IP</code> address-based method of transfer authorization, since attackers would not only need to have access to the <code class="systemitem">IP</code> address to transfer the zone, but they would also need to know the secret key.
+ </div><div class="para">
+ Since version 9, BIND also supports <em class="firstterm">TKEY</em>, which is another shared secret key method of authorizing zone transfers.
+ </div><div class="important"><div class="admonition_header"><h2>Secure the transfer</h2></div><div class="admonition"><div class="para">
+ When communicating over an insecure network, do not rely on <code class="systemitem">IP</code> address-based authentication only.
+ </div></div></div></div><div class="section" id="sec-bind-features-dnssec"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.6.4. DNS Security Extensions (DNSSEC)</h4></div></div></div><a id="idm225484501264" class="indexterm"></a><div class="para">
+ <em class="firstterm">Domain Name System Security Extensions</em> (<em class="firstterm">DNSSEC</em>) provide origin authentication of <code class="systemitem">DNS</code> data, authenticated denial of existence, and data integrity. When a particular domain is marked as secure, the <code class="literal">SERVFAIL</code> response is returned for each resource record that fails the validation.
+ </div><a id="idm225447949232" class="indexterm"></a><div class="para">
+ Note that to debug a DNSSEC-signed domain or a DNSSEC-aware resolver, you can use the <code class="command">dig</code> utility as described in <a class="xref" href="sec-bind-dig.html">Section 10.2.5, “Using the dig Utility”</a>. Useful options are <code class="option">+dnssec</code> (requests DNSSEC-related resource records by setting the DNSSEC OK bit), <code class="option">+cd</code> (tells recursive nameserver not to validate the response), and <code class="option">+bufsize=512</code> (changes the packet size to 512B to get through some firewalls).
+ </div></div><div class="section" id="sec-bind-features-ipv6"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.6.5. Internet Protocol version 6 (IPv6)</h4></div></div></div><a id="idm225446061696" class="indexterm"></a><div class="para">
+ <em class="firstterm">Internet Protocol version 6</em> (<em class="firstterm">IPv6</em>) is supported through the use of <code class="option">AAAA</code> resource records, and the <code class="option">listen-on-v6</code> directive as described in <a class="xref" href="sec-bind-namedconf.html#table-bind-namedconf-common-options">Table 10.3, “Commonly Used Configuration Options”</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-bind-dig.html"><strong>Prev</strong>10.2.5. Using the dig Utility</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-bind-mistakes.html"><strong>Next</strong>10.2.7. Common Mistakes to Avoid</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-mistakes.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-mistakes.html
new file mode 100644
index 0000000..290d672
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-mistakes.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.2.7. Common Mistakes to Avoid</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-BIND.html" title="10.2. BIND" /><link rel="prev" href="sec-bind-features.html" title="10.2.6. Advanced Features of BIND" /><link rel="next" href="sec-bind-additional-resources.html" title="10.2.8. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-bind-features.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="
sec-bind-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-bind-mistakes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.7. Common Mistakes to Avoid</h3></div></div></div><a id="idm225431685680" class="indexterm"></a><div class="para">
+ The following is a list of recommendations on how to avoid common mistakes users make when configuring a nameserver:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Use semicolons and curly brackets correctly</span></dt><dd><div class="para">
+ An omitted semicolon or unmatched curly bracket in the <code class="filename">/etc/named.conf</code> file can prevent the <code class="systemitem">named</code> service from starting.
+ </div></dd><dt class="varlistentry"><span class="term">Use period (the <code class="literal">.</code> character) correctly</span></dt><dd><div class="para">
+ In zone files, a period at the end of a domain name denotes a fully qualified domain name. If omitted, the <code class="systemitem">named</code> service will append the name of the zone or the value of <code class="option">$ORIGIN</code> to complete it.
+ </div></dd><dt class="varlistentry"><span class="term">Increment the serial number when editing a zone file</span></dt><dd><div class="para">
+ If the serial number is not incremented, the primary nameserver will have the correct, new information, but the secondary nameservers will never be notified of the change, and will not attempt to refresh their data of that zone.
+ </div></dd><dt class="varlistentry"><span class="term">Configure the firewall</span></dt><dd><div class="para">
+ If a firewall is blocking connections from the <code class="systemitem">named</code> service to other nameservers, the recommended practice is to change the firewall settings.
+ </div><div class="warning" id="warning-Warning-Avoid_Using_Fixed_UDP_Source_Ports"><div class="admonition_header"><h2>Avoid using fixed UDP source ports</h2></div><div class="admonition"><div class="para">
+ Using a fixed <code class="systemitem">UDP</code> source port for <code class="systemitem">DNS</code> queries is a potential security vulnerability that could allow an attacker to conduct cache-poisoning attacks more easily. To prevent this, by default <code class="systemitem">DNS</code> sends from a random ephemeral port. Configure your firewall to allow outgoing queries from a random <code class="systemitem">UDP</code> source port. The range <code class="literal">1024</code> to <code class="literal">65535</code> is used by default.
+ </div></div></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-bind-features.html"><strong>Prev</strong>10.2.6. Advanced Features of BIND</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-bind-additional-resources.html"><strong>Next</strong>10.2.8. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-namedconf.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-namedconf.html
new file mode 100644
index 0000000..043aa83
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-namedconf.html
@@ -0,0 +1,405 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.2.2. Configuring the named Service</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-BIND.html" title="10.2. BIND" /><link rel="prev" href="sec-BIND.html" title="10.2. BIND" /><link rel="next" href="sec-bind-zone.html" title="10.2.3. Editing Zone Files" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-BIND.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-bind-zone.html"><strong>Next</strong></a></li></ul><div
class="section" id="sec-bind-namedconf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.2. Configuring the named Service</h3></div></div></div><a id="idm225485993072" class="indexterm"></a><div class="para">
+ When the <code class="systemitem">named</code> service is started, it reads the configuration from the files as described in <a class="xref" href="sec-bind-namedconf.html#table-bind-namedconf-files">Table 10.1, “The named Service Configuration Files”</a>.
+ </div><a id="idm225485997360" class="indexterm"></a><a id="idm225485999200" class="indexterm"></a><a id="idm225486001248" class="indexterm"></a><div class="table" id="table-bind-namedconf-files"><h6>Table 10.1. The named Service Configuration Files</h6><div class="table-contents"><table summary="The named Service Configuration Files" border="1"><colgroup><col width="38%" class="path" /><col width="63%" class="description" /></colgroup><thead><tr><th class="">
+ Path
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="filename">/etc/named.conf</code>
+ </td><td class="">
+ The main configuration file.
+ </td></tr><tr><td class="">
+ <code class="filename">/etc/named/</code>
+ </td><td class="">
+ An auxiliary directory for configuration files that are included in the main configuration file.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The configuration file consists of a collection of statements with nested options surrounded by opening and closing curly brackets (<code class="literal">{</code> and <code class="literal">}</code>). Note that when editing the file, you have to be careful not to make any syntax error, otherwise the <code class="systemitem">named</code> service will not start. A typical <code class="filename">/etc/named.conf</code> file is organized as follows:
+ </div><pre class="programlisting"><em class="replaceable"><code>statement-1</code></em> ["<em class="replaceable"><code>statement-1-name</code></em>"] [<em class="replaceable"><code>statement-1-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};
+<em class="replaceable"><code>statement-2</code></em> ["<em class="replaceable"><code>statement-2-name</code></em>"] [<em class="replaceable"><code>statement-2-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};
+<em class="replaceable"><code>statement-N</code></em> ["<em class="replaceable"><code>statement-N-name</code></em>"] [<em class="replaceable"><code>statement-N-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};</pre><div class="note"><div class="admonition_header"><h2>Running BIND in a chroot environment</h2></div><div class="admonition"><div class="para">
+ If you have installed the <span class="package">bind-chroot</span> package, the BIND service will run in the <code class="command">chroot</code> environment. In that case, the initialization script will mount the above configuration files using the <code class="command">mount --bind</code> command, so that you can manage the configuration outside this environment. There is no need to copy anything into the <code class="filename">/var/named/chroot/</code> directory because it is mounted automatically. This simplifies maintenance since you do not need to take any special care of <code class="systemitem">BIND</code> configuration files if it is run in a <code class="command">chroot</code> environment. You can organize everything as you would with <code class="systemitem">BIND</code> not running in a <code class="command">chroot</code> environment.
+ </div><div class="para">
+ The following directories are automatically mounted into <code class="filename">/var/named/chroot/</code> if they are empty in the <code class="filename">/var/named/chroot/</code> directory. They must be kept empty if you want them to be mounted into <code class="filename">/var/named/chroot/</code>:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/etc/named</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/pki/dnssec-keys</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/run/named</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/var/named</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/lib64/bind</code> or <code class="filename">/usr/lib/bind</code> (architecture dependent).
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The following files are also mounted if the target file does not exist in <code class="filename">/var/named/chroot/</code>:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/etc/named.conf</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/rndc.conf</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/rndc.key</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/named.rfc1912.zones</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/named.dnssec.keys</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/named.iscdlv.key</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/named.root.key</code>
+ </div></li></ul></div>
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Editing files which have been mounted in a <code class="command">chroot</code> environment requires creating a backup copy and then editing the original file. Alternatively, use an editor with <span class="quote">“<span class="quote">edit-a-copy</span>”</span> mode disabled. For example, to edit the BIND's configuration file, <code class="filename">/etc/named.conf</code>, with Vim while it is running in a <code class="command">chroot</code> environment, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">vim -c "set backupcopy=yes" /etc/named.conf</code></pre>
+
+ </div></div></div><div class="section" id="sec-Installing_Bind_In_A_Chroot_Environment"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.2.1. Installing BIND in a chroot Environment</h4></div></div></div><div class="para">
+ To install <span class="application"><strong>BIND</strong></span> to run in a <code class="command">chroot</code> environment, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">yum install bind-chroot</code></pre>
+
+ </div><div class="para">
+ To enable the <code class="systemitem">named-chroot</code> service, first check if the <code class="systemitem">named</code> service is running by issuing the following command:
+<pre class="screen">~]$ <code class="command">systemctl status named</code></pre>
+ If it is running, it must be disabled.
+ </div><div class="para">
+ To disable <code class="systemitem">named</code>, issue the following commands as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl stop named</code></pre>
+
+<pre class="screen">~]# <code class="command">systemctl disable named</code></pre>
+ Then, to enable the <code class="systemitem">named-chroot</code> service, issue the following commands as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl enable named-chroot</code></pre>
+
+<pre class="screen">~]# <code class="command">systemctl start named-chroot</code></pre>
+
+ </div><div class="para">
+ To check the status of the <code class="systemitem">named-chroot</code> service, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl status named-chroot</code></pre>
+
+ </div></div><div class="section" id="sec-bind-namedconf-state"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.2.2. Common Statement Types</h4></div></div></div><div class="para">
+ The following types of statements are commonly used in <code class="filename">/etc/named.conf</code>:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225484885120" class="indexterm"></a>
+ <code class="option">acl</code> </span></dt><dd><div class="para">
+ The <code class="option">acl</code> (Access Control List) statement allows you to define groups of hosts, so that they can be permitted or denied access to the nameserver. It takes the following form:
+ </div><pre class="programlisting">acl <em class="replaceable"><code>acl-name</code></em> {
+ <em class="replaceable"><code>match-element</code></em>;
+ ...
+};</pre><div class="para">
+ The <em class="replaceable"><code>acl-name</code></em> statement name is the name of the access control list, and the <em class="replaceable"><code>match-element</code></em> option is usually an individual <code class="systemitem">IP</code> address (such as <code class="literal">10.0.1.1</code>) or a <em class="firstterm">Classless Inter-Domain Routing</em> (<acronym class="acronym">CIDR</acronym>) network notation (for example, <code class="literal">10.0.1.0/24</code>). For a list of already defined keywords, see <a class="xref" href="sec-bind-namedconf.html#table-bind-namedconf-common-acl">Table 10.2, “Predefined Access Control Lists”</a>.
+ </div><div class="table" id="table-bind-namedconf-common-acl"><h6>Table 10.2. Predefined Access Control Lists</h6><div class="table-contents"><table summary="Predefined Access Control Lists" border="1"><colgroup><col width="25%" class="keyword" /><col width="75%" class="description" /></colgroup><thead><tr><th class="">
+ Keyword
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="option">any</code>
+ </td><td class="">
+ Matches every <code class="systemitem">IP</code> address.
+ </td></tr><tr><td class="">
+ <code class="option">localhost</code>
+ </td><td class="">
+ Matches any <code class="systemitem">IP</code> address that is in use by the local system.
+ </td></tr><tr><td class="">
+ <code class="option">localnets</code>
+ </td><td class="">
+ Matches any <code class="systemitem">IP</code> address on any network to which the local system is connected.
+ </td></tr><tr><td class="">
+ <code class="option">none</code>
+ </td><td class="">
+ Does not match any <code class="systemitem">IP</code> address.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="option">acl</code> statement can be especially useful in conjunction with other statements such as <code class="option">options</code>. <a class="xref" href="sec-bind-namedconf.html#example-bind-namedconf-common-acl">Example 10.2, “Using acl in Conjunction with Options”</a> defines two access control lists, <code class="literal">black-hats</code> and <code class="literal">red-hats</code>, and adds <code class="literal">black-hats</code> on the blacklist while granting <code class="literal">red-hats</code> normal access.
+ </div><div class="example" id="example-bind-namedconf-common-acl"><h6>Example 10.2. Using acl in Conjunction with Options</h6><div class="example-contents"><pre class="programlisting">acl black-hats {
+ 10.0.2.0/24;
+ 192.168.0.0/24;
+ 1234:5678::9abc/24;
+};
+acl red-hats {
+ 10.0.1.0/24;
+};
+options {
+ blackhole { black-hats; };
+ allow-query { red-hats; };
+ allow-query-cache { red-hats; };
+};</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225483729472" class="indexterm"></a>
+ <code class="option">include</code> </span></dt><dd><div class="para">
+ The <code class="option">include</code> statement allows you to include files in the <code class="filename">/etc/named.conf</code>, so that potentially sensitive data can be placed in a separate file with restricted permissions. It takes the following form:
+ </div><pre class="programlisting">include "<em class="replaceable"><code>file-name</code></em>"</pre><div class="para">
+ The <em class="replaceable"><code>file-name</code></em> statement name is an absolute path to a file.
+ </div><div class="example" id="example-bind-namedconf-common-include"><h6>Example 10.3. Including a File to /etc/named.conf</h6><div class="example-contents"><pre class="programlisting">include "/etc/named.rfc1912.zones";</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225483738496" class="indexterm"></a>
+ <code class="option">options</code> </span></dt><dd><div class="para">
+ The <code class="option">options</code> statement allows you to define global server configuration options as well as to set defaults for other statements. It can be used to specify the location of the <code class="systemitem">named</code> working directory, the types of queries allowed, and much more. It takes the following form:
+ </div><pre class="programlisting">options {
+ <em class="replaceable"><code>option</code></em>;
+ ...
+};</pre><div class="para">
+ For a list of frequently used <em class="replaceable"><code>option</code></em> directives, see <a class="xref" href="sec-bind-namedconf.html#table-bind-namedconf-common-options">Table 10.3, “Commonly Used Configuration Options”</a> below.
+ </div><div class="table" id="table-bind-namedconf-common-options"><h6>Table 10.3. Commonly Used Configuration Options</h6><div class="table-contents"><table summary="Commonly Used Configuration Options" border="1"><colgroup><col width="25%" class="option" /><col width="75%" class="description" /></colgroup><thead><tr><th class="">
+ Option
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="option">allow-query</code>
+ </td><td class="">
+ Specifies which hosts are allowed to query the nameserver for authoritative resource records. It accepts an access control list, a collection of <code class="systemitem">IP</code> addresses, or networks in the CIDR notation. All hosts are allowed by default.
+ </td></tr><tr><td class="">
+ <code class="option">allow-query-cache</code>
+ </td><td class="">
+ Specifies which hosts are allowed to query the nameserver for non-authoritative data such as recursive queries. Only <code class="literal">localhost</code> and <code class="literal">localnets</code> are allowed by default.
+ </td></tr><tr><td class="">
+ <code class="option">blackhole</code>
+ </td><td class="">
+ Specifies which hosts are <span class="emphasis"><em>not</em></span> allowed to query the nameserver. This option should be used when a particular host or network floods the server with requests. The default option is <code class="literal">none</code>.
+ </td></tr><tr><td class="">
+ <code class="option">directory</code>
+ </td><td class="">
+ Specifies a working directory for the <code class="systemitem">named</code> service. The default option is <code class="literal">/var/named/</code>.
+ </td></tr><tr><td class="">
+ <code class="option">disable-empty-zone</code>
+ </td><td class="">
+ Used to disable one or more empty zones from the list of default prefixes that would be used. Can be specified in the options statement and also in view statements. It can be used multiple times.
+ </td></tr><tr><td class="">
+ <code class="option">dnssec-enable</code>
+ </td><td class="">
+ Specifies whether to return DNSSEC related resource records. The default option is <code class="literal">yes</code>.
+ </td></tr><tr><td class="">
+ <code class="option">dnssec-validation</code>
+ </td><td class="">
+ Specifies whether to prove that resource records are authentic via DNSSEC. The default option is <code class="literal">yes</code>.
+ </td></tr><tr><td class="">
+ <code class="option">empty-zones-enable</code>
+ </td><td class="">
+ Controls whether or not empty zones are created. Can be specified only in the options statement.
+ </td></tr><tr><td class="">
+ <code class="option">forwarders</code>
+ </td><td class="">
+ Specifies a list of valid <code class="systemitem">IP</code> addresses for nameservers to which the requests should be forwarded for resolution.
+ </td></tr><tr><td class="">
+ <code class="option">forward</code>
+ </td><td class="">
+ <div class="para">
+ Specifies the behavior of the <code class="option">forwarders</code> directive. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">first</code> — The server will query the nameservers listed in the <code class="option">forwarders</code> directive before attempting to resolve the name on its own.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">only</code> — When unable to query the nameservers listed in the <code class="option">forwarders</code> directive, the server will not attempt to resolve the name on its own.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="option">listen-on</code>
+ </td><td class="">
+ Specifies the <code class="systemitem">IPv4</code> network interface on which to listen for queries. On a <code class="systemitem">DNS</code> server that also acts as a gateway, you can use this option to answer queries originating from a single network only. All <code class="systemitem">IPv4</code> interfaces are used by default.
+ </td></tr><tr><td class="">
+ <code class="option">listen-on-v6</code>
+ </td><td class="">
+ Specifies the <code class="systemitem">IPv6</code> network interface on which to listen for queries. On a <code class="systemitem">DNS</code> server that also acts as a gateway, you can use this option to answer queries originating from a single network only. All <code class="systemitem">IPv6</code> interfaces are used by default.
+ </td></tr><tr><td class="">
+ <code class="option">max-cache-size</code>
+ </td><td class="">
+ Specifies the maximum amount of memory to be used for server caches. When the limit is reached, the server causes records to expire prematurely so that the limit is not exceeded. In a server with multiple views, the limit applies separately to the cache of each view. The default option is <code class="literal">32M</code>.
+ </td></tr><tr><td class="">
+ <code class="option">notify</code>
+ </td><td class="">
+ <div class="para">
+ Specifies whether to notify the secondary nameservers when a zone is updated. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">yes</code> — The server will notify all secondary nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">no</code> — The server will <span class="emphasis"><em>not</em></span> notify any secondary nameserver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">master-only</code> — The server will notify primary server for the zone only.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">explicit</code> — The server will notify only the secondary servers that are specified in the <code class="option">also-notify</code> list within a zone statement.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="option">pid-file</code>
+ </td><td class="">
+ Specifies the location of the process ID file created by the <code class="systemitem">named</code> service.
+ </td></tr><tr><td class="">
+ <code class="option">recursion</code>
+ </td><td class="">
+ Specifies whether to act as a recursive server. The default option is <code class="literal">yes</code>.
+ </td></tr><tr><td class="">
+ <code class="option">statistics-file</code>
+ </td><td class="">
+ Specifies an alternate location for statistics files. The <code class="filename">/var/named/named.stats</code> file is used by default.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The directory used by <code class="systemitem">named</code> for runtime data has been moved from the BIND default location, <code class="filename">/var/run/named/</code>, to a new location <code class="filename">/run/named/</code>. As a result, the PID file has been moved from the default location <code class="filename">/var/run/named/named.pid</code> to the new location <code class="filename">/run/named/named.pid</code>. In addition, the session-key file has been moved to <code class="filename">/run/named/session.key</code>. These locations need to be specified by statements in the options section. See <a class="xref" href="sec-bind-namedconf.html#example-bind-namedconf-common-options">Example 10.4, “Using the options Statement”</a>.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Restrict recursive servers to selected clients only</h2></div><div class="admonition"><div class="para">
+ To prevent distributed denial of service (DDoS) attacks, it is recommended that you use the <code class="option">allow-query-cache</code> option to restrict recursive <code class="systemitem">DNS</code> services for a particular subset of clients only.
+ </div></div></div><div class="para">
+ Refer to the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="sec-bind-additional-resources.html#sec-bind-installed-docs">Section 10.2.8.1, “Installed Documentation”</a>, and the <code class="filename">named.conf</code> manual page for a complete list of available options.
+ </div><div class="example" id="example-bind-namedconf-common-options"><h6>Example 10.4. Using the options Statement</h6><div class="example-contents"><pre class="programlisting">options {
+ allow-query { localhost; };
+ listen-on port 53 { 127.0.0.1; };
+ listen-on-v6 port 53 { ::1; };
+ max-cache-size 256M;
+ directory "/var/named";
+ statistics-file "/var/named/data/named_stats.txt";
+
+ recursion yes;
+ dnssec-enable yes;
+ dnssec-validation yes;
+
+ pid-file "/run/named/named.pid";
+ session-keyfile "/run/named/session.key";
+};</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225482243264" class="indexterm"></a>
+ <code class="option">zone</code> </span></dt><dd><div class="para">
+ The <code class="option">zone</code> statement allows you to define the characteristics of a zone, such as the location of its configuration file and zone-specific options, and can be used to override the global <code class="option">options</code> statements. It takes the following form:
+ </div><pre class="programlisting">zone <em class="replaceable"><code>zone-name</code></em> [<em class="replaceable"><code>zone-class</code></em>] {
+ <em class="replaceable"><code>option</code></em>;
+ ...
+};</pre><div class="para">
+ The <em class="replaceable"><code>zone-name</code></em> attribute is the name of the zone, <em class="replaceable"><code>zone-class</code></em> is the optional class of the zone, and <em class="replaceable"><code>option</code></em> is a <code class="option">zone</code> statement option as described in <a class="xref" href="sec-bind-namedconf.html#table-bind-namedconf-common-zone">Table 10.4, “Commonly Used Options in Zone Statements”</a>.
+ </div><div class="para">
+ The <em class="replaceable"><code>zone-name</code></em> attribute is particularly important, as it is the default value assigned for the <code class="option">$ORIGIN</code> directive used within the corresponding zone file located in the <code class="filename">/var/named/</code> directory. The <code class="systemitem">named</code> daemon appends the name of the zone to any non-fully qualified domain name listed in the zone file. For example, if a <code class="option">zone</code> statement defines the namespace for <code class="literal">example.com</code>, use <code class="literal">example.com</code> as the <em class="replaceable"><code>zone-name</code></em> so that it is placed at the end of host names within the <code class="literal">example.com</code> zone file.
+ </div><div class="para">
+ For more information about zone files, refer to <a class="xref" href="sec-bind-zone.html">Section 10.2.3, “Editing Zone Files”</a>.
+ </div><div class="table" id="table-bind-namedconf-common-zone"><h6>Table 10.4. Commonly Used Options in Zone Statements</h6><div class="table-contents"><table summary="Commonly Used Options in Zone Statements" border="1"><colgroup><col width="25%" class="option" /><col width="75%" class="description" /></colgroup><thead><tr><th class="">
+ Option
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="option">allow-query</code>
+ </td><td class="">
+ Specifies which clients are allowed to request information about this zone. This option overrides global <code class="option">allow-query</code> option. All query requests are allowed by default.
+ </td></tr><tr><td class="">
+ <code class="option">allow-transfer</code>
+ </td><td class="">
+ Specifies which secondary servers are allowed to request a transfer of the zone's information. All transfer requests are allowed by default.
+ </td></tr><tr><td class="">
+ <code class="option">allow-update</code>
+ </td><td class="">
+ <div class="para">
+ Specifies which hosts are allowed to dynamically update information in their zone. The default option is to deny all dynamic update requests.
+ </div>
+ <div class="para">
+ Note that you should be careful when allowing hosts to update information about their zone. Do not set <code class="systemitem">IP</code> addresses in this option unless the server is in the trusted network. Instead, use TSIG key as described in <a class="xref" href="sec-bind-features.html#sec-bind-features-tsig">Section 10.2.6.3, “Transaction SIGnatures (TSIG)”</a>.
+ </div>
+
+ </td></tr><tr><td class="">
+ <code class="option">file</code>
+ </td><td class="">
+ Specifies the name of the file in the <code class="systemitem">named</code> working directory that contains the zone's configuration data.
+ </td></tr><tr><td class="">
+ <code class="option">masters</code>
+ </td><td class="">
+ Specifies from which <code class="systemitem">IP</code> addresses to request authoritative zone information. This option is used only if the zone is defined as <code class="option">type</code> <code class="option">slave</code>.
+ </td></tr><tr><td class="">
+ <code class="option">notify</code>
+ </td><td class="">
+ <div class="para">
+ Specifies whether to notify the secondary nameservers when a zone is updated. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">yes</code> — The server will notify all secondary nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">no</code> — The server will <span class="emphasis"><em>not</em></span> notify any secondary nameserver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master-only</code> — The server will notify primary server for the zone only.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">explicit</code> — The server will notify only the secondary servers that are specified in the <code class="option">also-notify</code> list within a zone statement.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="option">type</code>
+ </td><td class="">
+ <div class="para">
+ Specifies the zone type. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">delegation-only</code> — Enforces the delegation status of infrastructure zones such as COM, NET, or ORG. Any answer that is received without an explicit or implicit delegation is treated as <code class="literal">NXDOMAIN</code>. This option is only applicable in TLDs (Top-Level Domain) or root zone files used in recursive or caching implementations.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">forward</code> — Forwards all requests for information about this zone to other nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">hint</code> — A special type of zone used to point to the root nameservers which resolve queries when a zone is not otherwise known. No configuration beyond the default is necessary with a <code class="option">hint</code> zone.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master</code> — Designates the nameserver as authoritative for this zone. A zone should be set as the <code class="option">master</code> if the zone's configuration files reside on the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">slave</code> — Designates the nameserver as a slave server for this zone. Master server is specified in <code class="option">masters</code> directive.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Most changes to the <code class="filename">/etc/named.conf</code> file of a primary or secondary nameserver involve adding, modifying, or deleting <code class="option">zone</code> statements, and only a small subset of <code class="option">zone</code> statement options is usually needed for a nameserver to work efficiently.
+ </div><div class="para">
+ In <a class="xref" href="sec-bind-namedconf.html#example-bind-namedconf-common-zone-primary">Example 10.5, “A Zone Statement for a Primary nameserver”</a>, the zone is identified as <code class="literal">example.com</code>, the type is set to <code class="literal">master</code>, and the <code class="systemitem">named</code> service is instructed to read the <code class="filename">/var/named/example.com.zone</code> file. It also allows only a secondary nameserver (<code class="literal">192.168.0.2</code>) to transfer the zone.
+ </div><div class="example" id="example-bind-namedconf-common-zone-primary"><h6>Example 10.5. A Zone Statement for a Primary nameserver</h6><div class="example-contents"><pre class="programlisting">zone "example.com" IN {
+ type master;
+ file "example.com.zone";
+ allow-transfer { 192.168.0.2; };
+};</pre></div></div><br class="example-break" /><div class="para">
+ A secondary server's <code class="option">zone</code> statement is slightly different. The type is set to <code class="literal">slave</code>, and the <code class="literal">masters</code> directive is telling <code class="systemitem">named</code> the <code class="systemitem">IP</code> address of the master server.
+ </div><div class="para">
+ In <a class="xref" href="sec-bind-namedconf.html#example-bind-namedconf-common-zone-secondary">Example 10.6, “A Zone Statement for a Secondary nameserver”</a>, the <code class="systemitem">named</code> service is configured to query the primary server at the <code class="literal">192.168.0.1</code> <code class="systemitem">IP</code> address for information about the <code class="literal">example.com</code> zone. The received information is then saved to the <code class="filename">/var/named/slaves/example.com.zone</code> file. Note that you have to put all slave zones in the <code class="filename">/var/named/slaves/</code> directory, otherwise the service will fail to transfer the zone.
+ </div><div class="example" id="example-bind-namedconf-common-zone-secondary"><h6>Example 10.6. A Zone Statement for a Secondary nameserver</h6><div class="example-contents"><pre class="programlisting">zone "example.com" {
+ type slave;
+ file "slaves/example.com.zone";
+ masters { 192.168.0.1; };
+};</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="sec-bind-namedconf-state-other"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.2.3. Other Statement Types</h4></div></div></div><div class="para">
+ The following types of statements are less commonly used in <code class="filename">/etc/named.conf</code>:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225480502864" class="indexterm"></a>
+ <code class="option">controls</code> </span></dt><dd><div class="para">
+ The <code class="option">controls</code> statement allows you to configure various security requirements necessary to use the <code class="command">rndc</code> command to administer the <code class="systemitem">named</code> service.
+ </div><div class="para">
+ Refer to <a class="xref" href="sec-bind-rndc.html">Section 10.2.4, “Using the rndc Utility”</a> for more information on the <code class="command">rndc</code> utility and its usage.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225489864112" class="indexterm"></a>
+ <code class="option">key</code> </span></dt><dd><div class="para">
+ The <code class="option">key</code> statement allows you to define a particular key by name. Keys are used to authenticate various actions, such as secure updates or the use of the <code class="command">rndc</code> command. Two options are used with <code class="option">key</code>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">algorithm <em class="replaceable"><code>algorithm-name</code></em></code> — The type of algorithm to be used (for example, <code class="literal">hmac-md5</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">secret "<em class="replaceable"><code>key-value</code></em>"</code> — The encrypted key.
+ </div></li></ul></div><div class="para">
+ Refer to <a class="xref" href="sec-bind-rndc.html">Section 10.2.4, “Using the rndc Utility”</a> for more information on the <code class="command">rndc</code> utility and its usage.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225489877600" class="indexterm"></a>
+ <code class="option">logging</code> </span></dt><dd><div class="para">
+ The <code class="option">logging</code> statement allows you to use multiple types of logs, so called <em class="firstterm">channels</em>. By using the <code class="option">channel</code> option within the statement, you can construct a customized type of log with its own file name (<code class="option">file</code>), size limit (<code class="option">size</code>), version number (<code class="option">version</code>), and level of importance (<code class="option">severity</code>). Once a customized channel is defined, a <code class="option">category</code> option is used to categorize the channel and begin logging when the <code class="systemitem">named</code> service is restarted.
+ </div><div class="para">
+ By default, <code class="systemitem">named</code> sends standard messages to the <code class="systemitem">rsyslog</code> daemon, which places them in <code class="filename">/var/log/messages</code>. Several standard channels are built into BIND with various severity levels, such as <code class="literal">default_syslog</code> (which handles informational logging messages) and <code class="literal">default_debug</code> (which specifically handles debugging messages). A default category, called <code class="literal">default</code>, uses the built-in channels to do normal logging without any special configuration.
+ </div><div class="para">
+ Customizing the logging process can be a very detailed process and is beyond the scope of this chapter. For information on creating custom BIND logs, refer to the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="sec-bind-additional-resources.html#sec-bind-installed-docs">Section 10.2.8.1, “Installed Documentation”</a>.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225482495712" class="indexterm"></a>
+ <code class="option">server</code> </span></dt><dd><div class="para">
+ The <code class="option">server</code> statement allows you to specify options that affect how the <code class="systemitem">named</code> service should respond to remote nameservers, especially with regard to notifications and zone transfers.
+ </div><div class="para">
+ The <code class="option">transfer-format</code> option controls the number of resource records that are sent with each message. It can be either <code class="literal">one-answer</code> (only one resource record), or <code class="literal">many-answers</code> (multiple resource records). Note that while the <code class="literal">many-answers</code> option is more efficient, it is not supported by older versions of BIND.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225482505360" class="indexterm"></a>
+ <code class="option">trusted-keys</code> </span></dt><dd><div class="para">
+ The <code class="option">trusted-keys</code> statement allows you to specify assorted public keys used for secure <code class="systemitem">DNS</code> (DNSSEC). Refer to <a class="xref" href="sec-bind-features.html#sec-bind-features-dnssec">Section 10.2.6.4, “DNS Security Extensions (DNSSEC)”</a> for more information on this topic.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225481386592" class="indexterm"></a>
+ <code class="option">view</code> </span></dt><dd><div class="para">
+ The <code class="option">view</code> statement allows you to create special views depending upon which network the host querying the nameserver is on. This allows some hosts to receive one answer regarding a zone while other hosts receive totally different information. Alternatively, certain zones may only be made available to particular trusted hosts while non-trusted hosts can only make queries for other zones.
+ </div><div class="para">
+ Multiple views can be used as long as their names are unique. The <code class="option">match-clients</code> option allows you to specify the <code class="systemitem">IP</code> addresses that apply to a particular view. If the <code class="option">options</code> statement is used within a view, it overrides the already configured global options. Finally, most <code class="option">view</code> statements contain multiple <code class="option">zone</code> statements that apply to the <code class="option">match-clients</code> list.
+ </div><div class="para">
+ Note that the order in which the <code class="option">view</code> statements are listed is important, as the first statement that matches a particular client's <code class="systemitem">IP</code> address is used. For more information on this topic, refer to <a class="xref" href="sec-bind-features.html#sec-bind-features-views">Section 10.2.6.1, “Multiple Views”</a>.
+ </div></dd></dl></div></div><div class="section" id="sec-bind-namedconf-comm"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.2.4. Comment Tags</h4></div></div></div><a id="idm225481381424" class="indexterm"></a><div class="para">
+ Additionally to statements, the <code class="filename">/etc/named.conf</code> file can also contain comments. Comments are ignored by the <code class="systemitem">named</code> service, but can prove useful when providing additional information to a user. The following are valid comment tags:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="literal">//</code> </span></dt><dd><div class="para">
+ Any text after the <code class="literal">//</code> characters to the end of the line is considered a comment. For example:
+ </div><pre class="programlisting">notify yes; // notify all secondary nameservers</pre></dd><dt class="varlistentry"><span class="term"> <code class="literal">#</code> </span></dt><dd><div class="para">
+ Any text after the <code class="literal">#</code> character to the end of the line is considered a comment. For example:
+ </div><pre class="programlisting">notify yes; # notify all secondary nameservers</pre></dd><dt class="varlistentry"><span class="term"><code class="literal">/*</code> and <code class="literal">*/</code></span></dt><dd><div class="para">
+ Any block of text enclosed in <code class="literal">/*</code> and <code class="literal">*/</code> is considered a comment. For example:
+ </div><pre class="programlisting">notify yes; /* notify all secondary nameservers */</pre></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-BIND.html"><strong>Prev</strong>10.2. BIND</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-bind-zone.html"><strong>Next</strong>10.2.3. Editing Zone Files</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-rndc.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-rndc.html
new file mode 100644
index 0000000..581beb2
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-rndc.html
@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.2.4. Using the rndc Utility</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-BIND.html" title="10.2. BIND" /><link rel="prev" href="sec-bind-zone.html" title="10.2.3. Editing Zone Files" /><link rel="next" href="sec-bind-dig.html" title="10.2.5. Using the dig Utility" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-bind-zone.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-bind-dig.html"><strong>Next
</strong></a></li></ul><div class="section" id="sec-bind-rndc"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.4. Using the rndc Utility</h3></div></div></div><a id="idm225463165520" class="indexterm"></a><div class="para">
+ The <code class="command">rndc</code> utility is a command-line tool that allows you to administer the <code class="systemitem">named</code> service, both locally and from a remote machine. Its usage is as follows:
+ </div><pre class="screen"><code class="command">rndc</code> [<em class="replaceable"><code>option</code></em>...] <em class="replaceable"><code>command</code></em> [<em class="replaceable"><code>command-option</code></em>]</pre><div class="section" id="sec-bind-rndc-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.4.1. Configuring the Utility</h4></div></div></div><div class="para">
+ To prevent unauthorized access to the service, <code class="systemitem">named</code> must be configured to listen on the selected port (<code class="literal">953</code> by default), and an identical key must be used by both the service and the <code class="command">rndc</code> utility.
+ </div><div class="table" id="table-bind-rndc-configuration-files"><h6>Table 10.7. Relevant files</h6><div class="table-contents"><table summary="Relevant files" border="1"><colgroup><col width="38%" class="path" /><col width="63%" class="description" /></colgroup><thead><tr><th class="">
+ Path
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <a id="idm225444383168" class="indexterm"></a>
+ <code class="filename">/etc/named.conf</code>
+ </td><td class="">
+ The default configuration file for the <code class="systemitem">named</code> service.
+ </td></tr><tr><td class="">
+ <a id="idm225438905568" class="indexterm"></a>
+ <code class="filename">/etc/rndc.conf</code>
+ </td><td class="">
+ The default configuration file for the <code class="command">rndc</code> utility.
+ </td></tr><tr><td class="">
+ <a id="idm225484503152" class="indexterm"></a>
+ <code class="filename">/etc/rndc.key</code>
+ </td><td class="">
+ The default key location.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="command">rndc</code> configuration is located in <code class="filename">/etc/rndc.conf</code>. If the file does not exist, the utility will use the key located in <code class="filename">/etc/rndc.key</code>, which was generated automatically during the installation process using the <code class="command">rndc-confgen -a</code> command.
+ </div><div class="para">
+ The <code class="systemitem">named</code> service is configured using the <code class="option">controls</code> statement in the <code class="filename">/etc/named.conf</code> configuration file as described in <a class="xref" href="sec-bind-namedconf.html#sec-bind-namedconf-state-other">Section 10.2.2.3, “Other Statement Types”</a>. Unless this statement is present, only the connections from the loopback address (<code class="systemitem">127.0.0.1</code>) will be allowed, and the key located in <code class="filename">/etc/rndc.key</code> will be used.
+ </div><div class="para">
+ For more information on this topic, refer to manual pages and the <em class="citetitle">BIND 9 Administrator Reference Manual</em> listed in <a class="xref" href="sec-bind-additional-resources.html">Section 10.2.8, “Additional Resources”</a>.
+ </div><div class="important"><div class="admonition_header"><h2>Set the correct permissions</h2></div><div class="admonition"><div class="para">
+ To prevent unprivileged users from sending control commands to the service, make sure only <code class="systemitem">root</code> is allowed to read the <code class="filename">/etc/rndc.key</code> file:
+ </div><pre class="screen">~]# <code class="command">chmod o-rwx /etc/rndc.key</code></pre></div></div></div><div class="section" id="sec-bind-rndc-status"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.4.2. Checking the Service Status</h4></div></div></div><div class="para">
+ To check the current status of the <code class="systemitem">named</code> service, use the following command:
+ </div><pre class="screen">~]# <code class="command">rndc status</code>
+version: 9.7.0-P2-RedHat-9.7.0-5.P2.el6
+CPUs found: 1
+worker threads: 1
+number of zones: 16
+debug level: 0
+xfers running: 0
+xfers deferred: 0
+soa queries in progress: 0
+query logging is OFF
+recursive clients: 0/0/1000
+tcp clients: 0/100
+server is up and running</pre></div><div class="section" id="sec-bind-rndc-reload"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.4.3. Reloading the Configuration and Zones</h4></div></div></div><div class="para">
+ To reload both the configuration file and zones, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">rndc reload</code>
+server reload successful</pre><div class="para">
+ This will reload the zones while keeping all previously cached responses, so that you can make changes to the zone files without losing all stored name resolutions.
+ </div><div class="para">
+ To reload a single zone, specify its name after the <code class="command">reload</code> command, for example:
+ </div><pre class="screen">~]# <code class="command">rndc reload localhost</code>
+zone reload up-to-date</pre><div class="para">
+ Finally, to reload the configuration file and newly added zones only, type:
+ </div><pre class="screen">~]# <code class="command">rndc reconfig</code></pre><div class="note"><div class="admonition_header"><h2>Modifying zones with dynamic DNS</h2></div><div class="admonition"><div class="para">
+ If you intend to manually modify a zone that uses Dynamic <code class="systemitem">DNS</code> (DDNS), make sure you run the <code class="command">freeze</code> command first:
+ </div><pre class="screen">~]# <code class="command">rndc freeze localhost</code></pre><div class="para">
+ Once you are finished, run the <code class="command">thaw</code> command to allow the <code class="systemitem">DDNS</code> again and reload the zone:
+ </div><pre class="screen">~]# <code class="command">rndc thaw localhost</code>
+The zone reload and thaw was successful.</pre></div></div></div><div class="section" id="sec-bind-rndc-sign"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.4.4. Updating Zone Keys</h4></div></div></div><div class="para">
+ To update the DNSSEC keys and sign the zone, use the <code class="command">sign</code> command. For example:
+ </div><pre class="screen">~]# <code class="command">rndc sign localhost</code></pre><div class="para">
+ Note that to sign a zone with the above command, the <code class="option">auto-dnssec</code> option has to be set to <code class="literal">maintain</code> in the zone statement. For example:
+ </div><pre class="programlisting">zone "localhost" IN {
+ type master;
+ file "named.localhost";
+ allow-update { none; };
+ auto-dnssec maintain;
+};</pre></div><div class="section" id="sec-bind-rndc-validation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.4.5. Enabling the DNSSEC Validation</h4></div></div></div><div class="para">
+ To enable the DNSSEC validation, issue the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">rndc validation on</code></pre><div class="para">
+ Similarly, to disable this option, type:
+ </div><pre class="screen">~]# <code class="command">rndc validation off</code></pre><div class="para">
+ Refer to the <code class="option">options</code> statement described in <a class="xref" href="sec-bind-namedconf.html#sec-bind-namedconf-state">Section 10.2.2.2, “Common Statement Types”</a> for information on how to configure this option in <code class="filename">/etc/named.conf</code>.
+ </div></div><div class="section" id="sec-bind-rndc-querylog"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.4.6. Enabling the Query Logging</h4></div></div></div><div class="para">
+ To enable (or disable in case it is currently enabled) the query logging, issue the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">rndc querylog</code></pre><div class="para">
+ To check the current setting, use the <code class="command">status</code> command as described in <a class="xref" href="sec-bind-rndc.html#sec-bind-rndc-status">Section 10.2.4.2, “Checking the Service Status”</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-bind-zone.html"><strong>Prev</strong>10.2.3. Editing Zone Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-bind-dig.html"><strong>Next</strong>10.2.5. Using the dig Utility</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-zone.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-zone.html
new file mode 100644
index 0000000..8c566b0
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-bind-zone.html
@@ -0,0 +1,255 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.2.3. Editing Zone Files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-BIND.html" title="10.2. BIND" /><link rel="prev" href="sec-bind-namedconf.html" title="10.2.2. Configuring the named Service" /><link rel="next" href="sec-bind-rndc.html" title="10.2.4. Using the rndc Utility" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-bind-namedconf.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-bind
-rndc.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-bind-zone"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.3. Editing Zone Files</h3></div></div></div><a id="idm225480737024" class="indexterm"></a><a id="idm225480732704" class="indexterm"></a><a id="idm225480734784" class="indexterm"></a><a id="idm225480737504" class="indexterm"></a><div class="para">
+ As outlined in <a class="xref" href="ch-DNS_Servers.html#sec-dns-introduction-zones">Section 10.1.1, “Nameserver Zones”</a>, zone files contain information about a namespace. They are stored in the <code class="systemitem">named</code> working directory located in <code class="filename">/var/named/</code> by default. Each zone file is named according to the <code class="option">file</code> option in the <code class="option">zone</code> statement, usually in a way that relates to the domain in and identifies the file as containing zone data, such as <code class="filename">example.com.zone</code>.
+ </div><div class="table" id="table-bind-zone-files"><h6>Table 10.5. The named Service Zone Files</h6><div class="table-contents"><table summary="The named Service Zone Files" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Path
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="filename">/var/named/</code>
+ </td><td class="">
+ The working directory for the <code class="systemitem">named</code> service. The nameserver is <span class="emphasis"><em>not</em></span> allowed to write to this directory.
+ </td></tr><tr><td class="">
+ <code class="filename">/var/named/slaves/</code>
+ </td><td class="">
+ The directory for secondary zones. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr><tr><td class="">
+ <code class="filename">/var/named/dynamic/</code>
+ </td><td class="">
+ The directory for other files, such as dynamic <code class="systemitem">DNS</code> (DDNS) zones or managed DNSSEC keys. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr><tr><td class="">
+ <code class="filename">/var/named/data/</code>
+ </td><td class="">
+ The directory for various statistics and debugging files. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ A zone file consists of directives and resource records. Directives tell the nameserver to perform tasks or apply special settings to the zone, resource records define the parameters of the zone and assign identities to individual hosts. While the directives are optional, the resource records are required in order to provide name service to a zone.
+ </div><div class="para">
+ All directives and resource records should be entered on individual lines.
+ </div><div class="section" id="sec-bind-zone-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.3.1. Common Directives</h4></div></div></div><div class="para">
+ Directives begin with the dollar sign character (<code class="literal">$</code>) followed by the name of the directive, and usually appear at the top of the file. The following directives are commonly used in zone files:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225486620528" class="indexterm"></a>
+ <code class="command">$INCLUDE</code> </span></dt><dd><div class="para">
+ The <code class="command">$INCLUDE</code> directive allows you to include another file at the place where it appears, so that other zone settings can be stored in a separate zone file.
+ </div><div class="example" id="example-bind-zone-directive-include"><h6>Example 10.7. Using the $INCLUDE Directive</h6><div class="example-contents"><pre class="programlisting">$INCLUDE /var/named/penguin.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225485723488" class="indexterm"></a>
+ <code class="command">$ORIGIN</code> </span></dt><dd><div class="para">
+ The <code class="command">$ORIGIN</code> directive allows you to append the domain name to unqualified records, such as those with the host name only. Note that the use of this directive is not necessary if the zone is specified in <code class="filename">/etc/named.conf</code>, since the zone name is used by default.
+ </div><div class="para">
+ In <a class="xref" href="sec-bind-zone.html#example-bind-zone-directive-origin">Example 10.8, “Using the $ORIGIN Directive”</a>, any names used in resource records that do not end in a trailing period (the <code class="literal">.</code> character) are appended with <code class="literal">example.com</code>.
+ </div><div class="example" id="example-bind-zone-directive-origin"><h6>Example 10.8. Using the $ORIGIN Directive</h6><div class="example-contents"><pre class="programlisting">$ORIGIN example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225485733648" class="indexterm"></a>
+ <code class="command">$TTL</code> </span></dt><dd><div class="para">
+ The <code class="command">$TTL</code> directive allows you to set the default <em class="firstterm">Time to Live</em> (TTL) value for the zone, that is, how long is a zone record valid. Each resource record can contain its own TTL value, which overrides this directive.
+ </div><div class="para">
+ Increasing this value allows remote nameservers to cache the zone information for a longer period of time, reducing the number of queries for the zone and lengthening the amount of time required to propagate resource record changes.
+ </div><div class="example" id="example-bind-zone-directive-ttl"><h6>Example 10.9. Using the $TTL Directive</h6><div class="example-contents"><pre class="programlisting">$TTL 1D</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="sec-bind-zone-rr"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.3.2. Common Resource Records</h4></div></div></div><div class="para">
+ The following resource records are commonly used in zone files:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225479874960" class="indexterm"></a>
+ <code class="command">A</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Address</em> record specifies an <code class="systemitem">IP</code> address to be assigned to a name. It takes the following form:
+ </div><pre class="programlisting"><em class="replaceable"><code>hostname</code></em> IN A <em class="replaceable"><code>IP-address</code></em></pre><div class="para">
+ If the <em class="replaceable"><code>hostname</code></em> value is omitted, the record will point to the last specified <em class="replaceable"><code>hostname</code></em>.
+ </div><div class="para">
+ In <a class="xref" href="sec-bind-zone.html#example-bind-zone-rr-a">Example 10.10, “Using the A Resource Record”</a>, the requests for <code class="systemitem">server1.example.com</code> are pointed to <code class="literal">10.0.1.3</code> or <code class="literal">10.0.1.5</code>.
+ </div><div class="example" id="example-bind-zone-rr-a"><h6>Example 10.10. Using the A Resource Record</h6><div class="example-contents"><pre class="programlisting">server1 IN A 10.0.1.3
+ IN A 10.0.1.5</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225479886992" class="indexterm"></a>
+ <code class="command">CNAME</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Canonical Name</em> record maps one name to another. Because of this, this type of record is sometimes referred to as an <em class="firstterm">alias record</em>. It takes the following form:
+ </div><pre class="programlisting"><em class="replaceable"><code>alias-name</code></em> IN CNAME <em class="replaceable"><code>real-name</code></em></pre><div class="para">
+ <code class="command">CNAME</code> records are most commonly used to point to services that use a common naming scheme, such as <code class="literal">www</code> for Web servers. However, there are multiple restrictions for their usage:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ CNAME records should not point to other CNAME records. This is mainly to avoid possible infinite loops.
+ </div></li><li class="listitem"><div class="para">
+ CNAME records should not contain other resource record types (such as A, NS, MX, etc.). The only exception are DNSSEC related records (RRSIG, NSEC, etc.) when the zone is signed.
+ </div></li><li class="listitem"><div class="para">
+ Other resource records that point to the fully qualified domain name (FQDN) of a host (NS, MX, PTR) should not point to a CNAME record.
+ </div></li></ul></div><div class="para">
+ In <a class="xref" href="sec-bind-zone.html#example-bind-zone-rr-cname">Example 10.11, “Using the CNAME Resource Record”</a>, the <code class="command">A</code> record binds a host name to an <code class="systemitem">IP</code> address, while the <code class="command">CNAME</code> record points the commonly used <code class="literal">www</code> host name to it.
+ </div><div class="example" id="example-bind-zone-rr-cname"><h6>Example 10.11. Using the CNAME Resource Record</h6><div class="example-contents"><pre class="programlisting">server1 IN A 10.0.1.5
+www IN CNAME server1</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225434398672" class="indexterm"></a>
+ <code class="command">MX</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Mail Exchange</em> record specifies where the mail sent to a particular namespace controlled by this zone should go. It takes the following form:
+ </div><pre class="programlisting">IN MX <em class="replaceable"><code>preference-value</code></em> <em class="replaceable"><code>email-server-name</code></em></pre><div class="para">
+ The <em class="replaceable"><code>email-server-name</code></em> is a fully qualified domain name (FQDN). The <em class="replaceable"><code>preference-value</code></em> allows numerical ranking of the email servers for a namespace, giving preference to some email systems over others. The <code class="command">MX</code> resource record with the lowest <em class="replaceable"><code>preference-value</code></em> is preferred over the others. However, multiple email servers can possess the same value to distribute email traffic evenly among them.
+ </div><div class="para">
+ In <a class="xref" href="sec-bind-zone.html#example-bind-zone-rr-mx">Example 10.12, “Using the MX Resource Record”</a>, the first <code class="systemitem">mail.example.com</code> email server is preferred to the <code class="systemitem">mail2.example.com</code> email server when receiving email destined for the <code class="systemitem">example.com</code> domain.
+ </div><div class="example" id="example-bind-zone-rr-mx"><h6>Example 10.12. Using the MX Resource Record</h6><div class="example-contents"><pre class="programlisting">example.com. IN MX 10 mail.example.com.
+ IN MX 20 mail2.example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225457666064" class="indexterm"></a>
+ <code class="command">NS</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Nameserver</em> record announces authoritative nameservers for a particular zone. It takes the following form:
+ </div><pre class="programlisting">IN NS <em class="replaceable"><code>nameserver-name</code></em></pre><div class="para">
+ The <em class="replaceable"><code>nameserver-name</code></em> should be a fully qualified domain name (FQDN). Note that when two nameservers are listed as authoritative for the domain, it is not important whether these nameservers are secondary nameservers, or if one of them is a primary server. They are both still considered authoritative.
+ </div><div class="example" id="example-bind-zone-rr-ns"><h6>Example 10.13. Using the NS Resource Record</h6><div class="example-contents"><pre class="programlisting">IN NS dns1.example.com.
+IN NS dns2.example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225457675408" class="indexterm"></a>
+ <code class="command">PTR</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Pointer</em> record points to another part of the namespace. It takes the following form:
+ </div><pre class="programlisting"><em class="replaceable"><code>last-IP-digit</code></em> IN PTR <em class="replaceable"><code>FQDN-of-system</code></em></pre><div class="para">
+ The <em class="replaceable"><code>last-IP-digit</code></em> directive is the last number in an <code class="systemitem">IP</code> address, and the <em class="replaceable"><code>FQDN-of-system</code></em> is a fully qualified domain name (FQDN).
+ </div><div class="para">
+ <code class="command">PTR</code> records are primarily used for reverse name resolution, as they point <code class="systemitem">IP</code> addresses back to a particular name. Refer to <a class="xref" href="sec-bind-zone.html#sec-bind-configuration-zone-reverse">Section 10.2.3.4.2, “A Reverse Name Resolution Zone File”</a> for examples of <code class="command">PTR</code> records in use.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225454262352" class="indexterm"></a>
+ <code class="command">SOA</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Start of Authority</em> record announces important authoritative information about a namespace to the nameserver. Located after the directives, it is the first resource record in a zone file. It takes the following form:
+ </div><pre class="programlisting">@ IN SOA <em class="replaceable"><code>primary-name-server</code></em> <em class="replaceable"><code>hostmaster-email</code></em> (
+ <em class="replaceable"><code>serial-number</code></em>
+ <em class="replaceable"><code>time-to-refresh</code></em>
+ <em class="replaceable"><code>time-to-retry</code></em>
+ <em class="replaceable"><code>time-to-expire</code></em>
+ <em class="replaceable"><code>minimum-TTL</code></em> )</pre><div class="para">
+ The directives are as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="literal">@</code> symbol places the <code class="command">$ORIGIN</code> directive (or the zone's name if the <code class="command">$ORIGIN</code> directive is not set) as the namespace being defined by this <code class="command">SOA</code> resource record.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>primary-name-server</code></em> directive is the host name of the primary nameserver that is authoritative for this domain.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>hostmaster-email</code></em> directive is the email of the person to contact about the namespace.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>serial-number</code></em> directive is a numerical value incremented every time the zone file is altered to indicate it is time for the <code class="systemitem">named</code> service to reload the zone.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>time-to-refresh</code></em> directive is the numerical value secondary nameservers use to determine how long to wait before asking the primary nameserver if any changes have been made to the zone.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>time-to-retry</code></em> directive is a numerical value used by secondary nameservers to determine the length of time to wait before issuing a refresh request in the event that the primary nameserver is not answering. If the primary server has not replied to a refresh request before the amount of time specified in the <em class="replaceable"><code>time-to-expire</code></em> directive elapses, the secondary servers stop responding as an authority for requests concerning that namespace.
+ </div></li><li class="listitem"><div class="para">
+ In BIND 4 and 8, the <em class="replaceable"><code>minimum-TTL</code></em> directive is the amount of time other nameservers cache the zone's information. In BIND 9, it defines how long negative answers are cached for. Caching of negative answers can be set to a maximum of 3 hours (<code class="option">3H</code>).
+ </div></li></ul></div><div class="para">
+ When configuring BIND, all times are specified in seconds. However, it is possible to use abbreviations when specifying units of time other than seconds, such as minutes (<code class="literal">M</code>), hours (<code class="literal">H</code>), days (<code class="literal">D</code>), and weeks (<code class="literal">W</code>). <a class="xref" href="sec-bind-zone.html#tb-bind-seconds">Table 10.6, “Seconds compared to other time units”</a> shows an amount of time in seconds and the equivalent time in another format.
+ </div><div class="table" id="tb-bind-seconds"><h6>Table 10.6. Seconds compared to other time units</h6><div class="table-contents"><table summary="Seconds compared to other time units" border="1"><colgroup><col width="50%" class="seconds" /><col width="50%" class="other" /></colgroup><thead><tr><th class="">
+ Seconds
+ </th><th class="">
+ Other Time Units
+ </th></tr></thead><tbody><tr><td class="">
+ 60
+ </td><td class="">
+ <code class="literal">1M</code>
+ </td></tr><tr><td class="">
+ 1800
+ </td><td class="">
+ <code class="literal">30M</code>
+ </td></tr><tr><td class="">
+ 3600
+ </td><td class="">
+ <code class="literal">1H</code>
+ </td></tr><tr><td class="">
+ 10800
+ </td><td class="">
+ <code class="literal">3H</code>
+ </td></tr><tr><td class="">
+ 21600
+ </td><td class="">
+ <code class="literal">6H</code>
+ </td></tr><tr><td class="">
+ 43200
+ </td><td class="">
+ <code class="literal">12H</code>
+ </td></tr><tr><td class="">
+ 86400
+ </td><td class="">
+ <code class="literal">1D</code>
+ </td></tr><tr><td class="">
+ 259200
+ </td><td class="">
+ <code class="literal">3D</code>
+ </td></tr><tr><td class="">
+ 604800
+ </td><td class="">
+ <code class="literal">1W</code>
+ </td></tr><tr><td class="">
+ 31536000
+ </td><td class="">
+ <code class="literal">365D</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-bind-zone-rr-soa"><h6>Example 10.14. Using the SOA Resource Record</h6><div class="example-contents"><pre class="programlisting">@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="sec-bind-zone-comm"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.3.3. Comment Tags</h4></div></div></div><a id="idm225487231504" class="indexterm"></a><div class="para">
+ Additionally to resource records and directives, a zone file can also contain comments. Comments are ignored by the <code class="systemitem">named</code> service, but can prove useful when providing additional information to the user. Any text after the semicolon character (<code class="literal">;</code>) to the end of the line is considered a comment. For example:
+ </div><pre class="programlisting"> 604800 ; expire after 1 week</pre></div><div class="section" id="sec-bind-zone-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.2.3.4. Example Usage</h4></div></div></div><div class="para">
+ The following examples show the basic usage of zone files.
+ </div><div class="section" id="sec-bind-zone-examples-basic"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">10.2.3.4.1. A Simple Zone File</h5></div></div></div><a id="idm225487237888" class="indexterm"></a><div class="para">
+ <a class="xref" href="sec-bind-zone.html#example-bind-zone-examples-basic">Example 10.15, “A simple zone file”</a> demonstrates the use of standard directives and <code class="command">SOA</code> values.
+ </div><div class="example" id="example-bind-zone-examples-basic"><h6>Example 10.15. A simple zone file</h6><div class="example-contents"><pre class="programlisting">$ORIGIN example.com.
+$TTL 86400
+@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day
+;
+;
+ IN NS dns1.example.com.
+ IN NS dns2.example.com.
+dns1 IN A 10.0.1.1
+ IN AAAA aaaa:bbbb::1
+dns2 IN A 10.0.1.2
+ IN AAAA aaaa:bbbb::2
+;
+;
+@ IN MX 10 mail.example.com.
+ IN MX 20 mail2.example.com.
+mail IN A 10.0.1.5
+ IN AAAA aaaa:bbbb::5
+mail2 IN A 10.0.1.6
+ IN AAAA aaaa:bbbb::6
+;
+;
+; This sample zone file illustrates sharing the same IP addresses
+; for multiple services:
+;
+services IN A 10.0.1.10
+ IN AAAA aaaa:bbbb::10
+ IN A 10.0.1.11
+ IN AAAA aaaa:bbbb::11
+
+ftp IN CNAME services.example.com.
+www IN CNAME services.example.com.
+;
+;</pre></div></div><br class="example-break" /><div class="para">
+ In this example, the authoritative nameservers are set as <code class="systemitem">dns1.example.com</code> and <code class="systemitem">dns2.example.com</code>, and are tied to the <code class="systemitem">10.0.1.1</code> and <code class="systemitem">10.0.1.2</code> <code class="systemitem">IP</code> addresses respectively using the <code class="command">A</code> record.
+ </div><div class="para">
+ The email servers configured with the <code class="command">MX</code> records point to <code class="systemitem">mail</code> and <code class="systemitem">mail2</code> via <code class="command">A</code> records. Since these names do not end in a trailing period (<code class="literal">.</code> character), the <code class="command">$ORIGIN</code> domain is placed after them, expanding them to <code class="systemitem">mail.example.com</code> and <code class="systemitem">mail2.example.com</code>.
+ </div><div class="para">
+ Services available at the standard names, such as <code class="systemitem">www.example.com</code> (<acronym class="acronym">WWW</acronym>), are pointed at the appropriate servers using the <code class="command">CNAME</code> record.
+ </div><div class="para">
+ This zone file would be called into service with a <code class="command">zone</code> statement in the <code class="filename">/etc/named.conf</code> similar to the following:
+ </div><pre class="programlisting">zone "example.com" IN {
+ type master;
+ file "example.com.zone";
+ allow-update { none; };
+};</pre></div><div class="section" id="sec-bind-configuration-zone-reverse"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">10.2.3.4.2. A Reverse Name Resolution Zone File</h5></div></div></div><a id="idm225457665296" class="indexterm"></a><div class="para">
+ A reverse name resolution zone file is used to translate an <code class="systemitem">IP</code> address in a particular namespace into a fully qualified domain name (FQDN). It looks very similar to a standard zone file, except that the <code class="command">PTR</code> resource records are used to link the <code class="systemitem">IP</code> addresses to a fully qualified domain name as shown in <a class="xref" href="sec-bind-zone.html#example-bind-zone-examples-reverse">Example 10.16, “A reverse name resolution zone file”</a>.
+ </div><div class="example" id="example-bind-zone-examples-reverse"><h6>Example 10.16. A reverse name resolution zone file</h6><div class="example-contents"><pre class="programlisting">$ORIGIN 1.0.10.in-addr.arpa.
+$TTL 86400
+@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day
+;
+@ IN NS dns1.example.com.
+;
+1 IN PTR dns1.example.com.
+2 IN PTR dns2.example.com.
+;
+5 IN PTR server1.example.com.
+6 IN PTR server2.example.com.
+;
+3 IN PTR ftp.example.com.
+4 IN PTR ftp.example.com.</pre></div></div><br class="example-break" /><div class="para">
+ In this example, <code class="systemitem">IP</code> addresses <code class="systemitem">10.0.1.1</code> through <code class="systemitem">10.0.1.6</code> are pointed to the corresponding fully qualified domain name.
+ </div><div class="para">
+ This zone file would be called into service with a <code class="option">zone</code> statement in the <code class="filename">/etc/named.conf</code> file similar to the following:
+ </div><pre class="programlisting">zone "1.0.10.in-addr.arpa" IN {
+ type master;
+ file "example.com.rr.zone";
+ allow-update { none; };
+};</pre><div class="para">
+ There is very little difference between this example and a standard <code class="command">zone</code> statement, except for the zone name. Note that a reverse name resolution zone requires the first three blocks of the <code class="systemitem">IP</code> address reversed followed by <code class="command">.in-addr.arpa</code>. This allows the single block of <code class="systemitem">IP</code> numbers used in the reverse name resolution zone file to be associated with the zone.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-bind-namedconf.html"><strong>Prev</strong>10.2.2. Configuring the named Service</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-bind-rndc.html"><strong>Next</strong>10.2.4. Using the rndc Utility</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-dhcp-additional-resources.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-dhcp-additional-resources.html
new file mode 100644
index 0000000..f1935fa
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-dhcp-additional-resources.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.6. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-DHCP_Servers.html" title="Chapter 9. DHCP Servers" /><link rel="prev" href="sec-dhcp_for_ipv6_dhcpv6.html" title="9.5. DHCP for IPv6 (DHCPv6)" /><link rel="next" href="ch-DNS_Servers.html" title="Chapter 10. DNS Servers" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-dhcp_for_ipv6_dhcpv6.html"><strong>Prev</strong></a></li><li class="next"><a accesskey=
"n" href="ch-DNS_Servers.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-dhcp-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.6. Additional Resources</h2></div></div></div><a id="idm225466780848" class="indexterm"></a><div class="para">
+ For additional information, see <em class="citetitle">The DHCP Handbook; Ralph Droms and Ted Lemon; 2003</em> or the following resources.
+ </div><div class="section" id="sec-dhcp-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.6.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">dhcpd(8)</code> man page — Describes how the <code class="systemitem">DHCP</code> daemon works.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcpd.conf(5)</code> man page — Explains how to configure the <code class="systemitem">DHCP</code> configuration file; includes some examples.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcpd.leases(5)</code> man page — Describes a persistent database of leases.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcp-options(5)</code> man page — Explains the syntax for declaring <code class="systemitem">DHCP</code> options in <code class="filename">dhcpd.conf</code>; includes some examples.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcrelay(8)</code> man page — Explains the <code class="systemitem">DHCP</code> Relay Agent and its configuration options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/dhcp/</code> — Contains example configuration files.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/dhcp-common/</code> — Contains README files, and release notes for current versions of the <code class="systemitem">DHCP</code> service.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-dhcp_for_ipv6_dhcpv6.html"><strong>Prev</strong>9.5. DHCP for IPv6 (DHCPv6)</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-DNS_Servers.html"><strong>Next</strong>Chapter 10. DNS Servers</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-dhcp-configuring-server.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-dhcp-configuring-server.html
new file mode 100644
index 0000000..32fe803
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-dhcp-configuring-server.html
@@ -0,0 +1,112 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.2. Configuring a DHCP Server</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-DHCP_Servers.html" title="Chapter 9. DHCP Servers" /><link rel="prev" href="ch-DHCP_Servers.html" title="Chapter 9. DHCP Servers" /><link rel="next" href="lease-database.html" title="9.2.2. Lease Database" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-DHCP_Servers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="lease-database
.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-dhcp-configuring-server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.2. Configuring a DHCP Server</h2></div></div></div><a id="idm225443648576" class="indexterm"></a><div class="para">
+ The <span class="package">dhcp</span> package contains an <em class="firstterm">Internet Systems Consortium</em> (<acronym class="acronym">ISC</acronym>) <code class="systemitem">DHCP</code> server. Install the package as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">yum install dhcp</code>
+</pre><div class="para">
+ Installing the <span class="package">dhcp</span> package creates a file, <code class="filename">/etc/dhcp/dhcpd.conf</code>, which is merely an empty configuration file. As <code class="systemitem">root</code>, issue the following command:
+ </div><pre class="programlisting">~]# <code class="command">cat /etc/dhcp/dhcpd.conf</code>
+#
+# DHCP Server Configuration file.
+# see /usr/share/doc/dhcp/dhcpd.conf.example
+# see dhcpd.conf(5) man page
+#</pre><div class="para">
+ The example configuration file can be found at <code class="filename">/usr/share/doc/dhcp/dhcpd.conf.example</code>. You should use this file to help you configure <code class="filename">/etc/dhcp/dhcpd.conf</code>, which is explained in detail below.
+ </div><div class="para">
+ <code class="systemitem">DHCP</code> also uses the file <code class="filename">/var/lib/dhcpd/dhcpd.leases</code> to store the client lease database. Refer to <a class="xref" href="lease-database.html">Section 9.2.2, “Lease Database”</a> for more information.
+ </div><div class="section" id="config-file"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.2.1. Configuration File</h3></div></div></div><a id="idm225446106912" class="indexterm"></a><a id="idm225446105472" class="indexterm"></a><div class="para">
+ The first step in configuring a <code class="systemitem">DHCP</code> server is to create the configuration file that stores the network information for the clients. Use this file to declare options for client systems.
+ </div><div class="para">
+ The configuration file can contain extra tabs or blank lines for easier formatting. Keywords are case-insensitive and lines beginning with a hash sign (<code class="literal">#</code>) are considered comments.
+ </div><div class="para">
+ There are two types of statements in the configuration file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Parameters — State how to perform a task, whether to perform a task, or what network configuration options to send to the client.
+ </div></li><li class="listitem"><div class="para">
+ Declarations — Describe the topology of the network, describe the clients, provide addresses for the clients, or apply a group of parameters to a group of declarations.
+ </div></li></ul></div><a id="idm225443585584" class="indexterm"></a><div class="para">
+ The parameters that start with the keyword option are referred to as <em class="firstterm">options</em>. These options control <code class="systemitem">DHCP</code> options; whereas, parameters configure values that are not optional or control how the <code class="systemitem">DHCP</code> server behaves.
+ </div><a id="idm225443581936" class="indexterm"></a><div class="para">
+ Parameters (including options) declared before a section enclosed in curly brackets (<code class="literal">{ }</code>) are considered global parameters. Global parameters apply to all the sections below it.
+ </div><div class="important"><div class="admonition_header"><h2>Restart the DHCP Daemon for the Changes to Take Effect</h2></div><div class="admonition"><div class="para">
+ If the configuration file is changed, the changes do not take effect until the <code class="systemitem">DHCP</code> daemon is restarted with the command <code class="command">systemctl restart dhcpd</code>.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Use the omshell Command</h2></div><div class="admonition"><div class="para">
+ Instead of changing a <code class="systemitem">DHCP</code> configuration file and restarting the service each time, using the <code class="command">omshell</code> command provides an interactive way to connect to, query, and change the configuration of a <code class="systemitem">DHCP</code> server. By using <code class="command">omshell</code>, all changes can be made while the server is running. For more information on <code class="command">omshell</code>, see the <code class="command">omshell</code> man page.
+ </div></div></div><div class="para">
+ In <a class="xref" href="sec-dhcp-configuring-server.html#subnet">Example 9.1, “Subnet Declaration”</a>, the <code class="command">routers</code>, <code class="command">subnet-mask</code>, <code class="command">domain-search</code>, <code class="command">domain-name-servers</code>, and <code class="command">time-offset</code> options are used for any <code class="command">host</code> statements declared below it.
+ </div><a id="idm225446757552" class="indexterm"></a><div class="para">
+ For every subnet which will be served, and for every subnet to which the <code class="systemitem">DHCP</code> server is connected, there must be one <code class="command">subnet</code> declaration, which tells the <code class="systemitem">DHCP</code> daemon how to recognize that an address is on that subnet. A <code class="command">subnet</code> declaration is required for each subnet even if no addresses will be dynamically allocated to that subnet.
+ </div><div class="para">
+ In this example, there are global options for every <code class="systemitem">DHCP</code> client in the subnet and a <code class="command">range</code> declared. Clients are assigned an <code class="systemitem">IP</code> address within the <code class="command">range</code>.
+ </div><div class="example" id="subnet"><h6>Example 9.1. Subnet Declaration</h6><div class="example-contents"><pre class="programlisting">subnet 192.168.1.0 netmask 255.255.255.0 {
+ option routers 192.168.1.254;
+ option subnet-mask 255.255.255.0;
+ option domain-search "example.com";
+ option domain-name-servers 192.168.1.1;
+ option time-offset -18000; # Eastern Standard Time
+ range 192.168.1.10 192.168.1.100;
+}</pre></div></div><br class="example-break" /><div class="para">
+ To configure a <code class="systemitem">DHCP</code> server that leases a dynamic <code class="systemitem">IP</code> address to a system within a subnet, modify the example values from <a class="xref" href="sec-dhcp-configuring-server.html#dynamic-ip">Example 9.2, “Range Parameter”</a>. It declares a default lease time, maximum lease time, and network configuration values for the clients. This example assigns <code class="systemitem">IP</code> addresses in the <code class="command">range</code> <code class="systemitem">192.168.1.10</code> and <code class="systemitem">192.168.1.100</code> to client systems.
+ </div><div class="example" id="dynamic-ip"><h6>Example 9.2. Range Parameter</h6><div class="example-contents"><pre class="programlisting">default-lease-time 600;
+max-lease-time 7200;
+option subnet-mask 255.255.255.0;
+option broadcast-address 192.168.1.255;
+option routers 192.168.1.254;
+option domain-name-servers 192.168.1.1, 192.168.1.2;
+option domain-search "example.com";
+subnet 192.168.1.0 netmask 255.255.255.0 {
+ range 192.168.1.10 192.168.1.100;
+}</pre></div></div><br class="example-break" /><div class="para">
+ To assign an <code class="systemitem">IP</code> address to a client based on the MAC address of the network interface card, use the <code class="command">hardware ethernet</code> parameter within a <code class="command">host</code> declaration. As demonstrated in <a class="xref" href="sec-dhcp-configuring-server.html#static-ip">Example 9.3, “Static IP Address Using DHCP”</a>, the <code class="command">host apex</code> declaration specifies that the network interface card with the MAC address <code class="systemitem">00:A0:78:8E:9E:AA</code> always receives the <code class="systemitem">IP</code> address <code class="systemitem">192.168.1.4</code>.
+ </div><div class="para">
+ Note that you can also use the optional parameter <code class="option">host-name</code> to assign a host name to the client.
+ </div><div class="example" id="static-ip"><h6>Example 9.3. Static IP Address Using DHCP</h6><div class="example-contents"><pre class="programlisting">host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}</pre></div></div><br class="example-break" /><a id="idm225452632784" class="indexterm"></a><div class="para">
+ All subnets that share the same physical network should be declared within a <code class="command">shared-network</code> declaration as shown in <a class="xref" href="sec-dhcp-configuring-server.html#shared-network">Example 9.4, “Shared-network Declaration”</a>. Parameters within the <code class="command">shared-network</code>, but outside the enclosed subnet declarations, are considered to be global parameters. The name assigned to <code class="command">shared-network</code> must be a descriptive title for the network, such as using the title <span class="quote">“<span class="quote">test-lab</span>”</span> to describe all the subnets in a test lab environment.
+ </div><div class="example" id="shared-network"><h6>Example 9.4. Shared-network Declaration</h6><div class="example-contents"><pre class="programlisting">shared-network name {
+ option domain-search "test.redhat.com";
+ option domain-name-servers ns1.redhat.com, ns2.redhat.com;
+ option routers 192.168.0.254;
+ #more parameters for EXAMPLE shared-network
+ subnet 192.168.1.0 netmask 255.255.252.0 {
+ #parameters for subnet
+ range 192.168.1.1 192.168.1.254;
+ }
+ subnet 192.168.2.0 netmask 255.255.252.0 {
+ #parameters for subnet
+ range 192.168.2.1 192.168.2.254;
+ }
+}</pre></div></div><br class="example-break" /><a id="idm225452626192" class="indexterm"></a><div class="para">
+ As demonstrated in <a class="xref" href="sec-dhcp-configuring-server.html#group">Example 9.5, “Group Declaration”</a>, the <code class="command">group</code> declaration is used to apply global parameters to a group of declarations. For example, shared networks, subnets, and hosts can be grouped.
+ </div><div class="example" id="group"><h6>Example 9.5. Group Declaration</h6><div class="example-contents"><pre class="programlisting">group {
+ option routers 192.168.1.254;
+ option subnet-mask 255.255.255.0;
+ option domain-search "example.com";
+ option domain-name-servers 192.168.1.1;
+ option time-offset -18000; # Eastern Standard Time
+ host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+ }
+ host raleigh {
+ option host-name "raleigh.example.com";
+ hardware ethernet 00:A1:DD:74:C3:F2;
+ fixed-address 192.168.1.6;
+ }
+}</pre></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Using the Example Configuration File</h2></div><div class="admonition"><div class="para">
+ You can use the provided example configuration file as a starting point and add custom configuration options to it. To copy this file to the proper location, use the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">cp /usr/share/doc/dhcp-<em class="replaceable"><code>version_number</code></em>/dhcpd.conf.example /etc/dhcp/dhcpd.conf</code></pre><div class="para">
+ ... where <em class="replaceable"><code>version_number</code></em> is the <code class="systemitem">DHCP</code> version number.
+ </div></div></div><div class="para">
+ For a complete list of option statements and what they do, see the <code class="filename">dhcp-options(5)</code> man page.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-DHCP_Servers.html"><strong>Prev</strong>Chapter 9. DHCP Servers</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="lease-database.html"><strong>Next</strong>9.2.2. Lease Database</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-dhcp_for_ipv6_dhcpv6.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-dhcp_for_ipv6_dhcpv6.html
new file mode 100644
index 0000000..5ec9ee7
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-dhcp_for_ipv6_dhcpv6.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.5. DHCP for IPv6 (DHCPv6)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-DHCP_Servers.html" title="Chapter 9. DHCP Servers" /><link rel="prev" href="sec-Configuring_a_Multihomed_DHCP_Server.html" title="9.4. Configuring a Multihomed DHCP Server" /><link rel="next" href="sec-dhcp-additional-resources.html" title="9.6. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_a_Multihomed_DHCP_Server.html
"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-dhcp-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-dhcp_for_ipv6_dhcpv6"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.5. DHCP for IPv6 (DHCPv6)</h2></div></div></div><a id="idm225450692416" class="indexterm"></a><a id="idm225450690976" class="indexterm"></a><div class="para">
+ The ISC <code class="systemitem">DHCP</code> includes support for <code class="systemitem">IPv6</code> (<code class="systemitem">DHCPv6</code>) since the 4.x release with a <code class="systemitem">DHCPv6</code> server, client, and relay agent functionality. The agents support both <code class="systemitem">IPv4</code> and <code class="systemitem">IPv6</code>, however the agents can only manage one protocol at a time; for dual support they must be started separately for <code class="systemitem">IPv4</code> and <code class="systemitem">IPv6</code>. For example, configure both <code class="systemitem">DHCPv4</code> and <code class="systemitem">DHCPv6</code> by editing their respective configuration files <code class="filename">/etc/dhcp/dhcpd.conf</code> and <code class="filename">/etc/dhcp/dhcpd6.conf</code> and then issue the following commands:
+<pre class="screen">~]# <code class="command">systemctl start dhcpd</code>
+~]# <code class="command">systemctl start dhcpd6</code></pre>
+
+ </div><div class="para">
+ The <code class="systemitem">DHCPv6</code> server configuration file can be found at <code class="filename">/etc/dhcp/dhcpd6.conf</code>.
+ </div><div class="para">
+ The example server configuration file can be found at <code class="filename">/usr/share/doc/dhcp/dhcpd6.conf.example</code>.
+ </div><div class="para">
+ A simple <code class="systemitem">DHCPv6</code> server configuration file can look like this:
+ </div><pre class="programlisting">subnet6 2001:db8:0:1::/64 {
+ range6 2001:db8:0:1::129 2001:db8:0:1::254;
+ option dhcp6.name-servers fec0:0:0:1::1;
+ option dhcp6.domain-search "domain.example";
+}</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_a_Multihomed_DHCP_Server.html"><strong>Prev</strong>9.4. Configuring a Multihomed DHCP Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-dhcp-additional-resources.html"><strong>Next</strong>9.6. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-hostnamectl-Online_Documentation.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-hostnamectl-Online_Documentation.html
new file mode 100644
index 0000000..c9bbd71
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-hostnamectl-Online_Documentation.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.4.2. Online Documentation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-additional_resources.html" title="3.4. Additional Resources" /><link rel="prev" href="sec-additional_resources.html" title="3.4. Additional Resources" /><link rel="next" href="ch-Configure_Network_Bonding.html" title="Chapter 4. Configure Network Bonding" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-additional_resources.html"><strong>Prev</strong></a>
</li><li class="next"><a accesskey="n" href="ch-Configure_Network_Bonding.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-hostnamectl-Online_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.4.2. Online Documentation</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.freedesktop.org/wiki/Software/systemd/hostnamed">http://www.freedesktop.org/wiki/Software/systemd/hostnamed</a></span></dt><dd><div class="para">
+ Information on <code class="systemitem">systemd-hostnamed</code>.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-additional_resources.html"><strong>Prev</strong>3.4. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Configure_Network_Bonding.html"><strong>Next</strong>Chapter 4. Configure Network Bonding</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec-teamd_docs-online.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-teamd_docs-online.html
new file mode 100644
index 0000000..8a3e44a
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec-teamd_docs-online.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.14.2. Online Documentation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec-Network_Teaming-additional_resources.html" title="5.14. Additional Resources" /><link rel="prev" href="sec-Network_Teaming-additional_resources.html" title="5.14. Additional Resources" /><link rel="next" href="ch-Configure_Network_Bridging.html" title="Chapter 6. Configure Network Bridging" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Network_Teaming-
additional_resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Configure_Network_Bridging.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-teamd_docs-online"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.14.2. Online Documentation</h3></div></div></div><div class="para">
+ <div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.libteam.org">http://www.libteam.org</a></span></dt><dd><div class="para">
+ The upstream project.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.w3schools.com/json/json_syntax.asp">http://www.w3schools.com/json/json_syntax.asp</a></span></dt><dd><div class="para">
+ An explanation of JSON syntax.
+ </div></dd></dl></div>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Network_Teaming-additional_resources.html"><strong>Prev</strong>5.14. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Configure_Network_Bridging.html"><strong>Next</strong>Chapter 6. Configure Network Bridging</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Changing_Host_Names_Remotely.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Changing_Host_Names_Remotely.html
new file mode 100644
index 0000000..97eb73e
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Changing_Host_Names_Remotely.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.5. Changing Host Names Remotely</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec_Configuring_Host_Names_Using_hostnamectl.html" title="3.2. Configuring Host Names Using hostnamectl" /><link rel="prev" href="sec_Clear_a_Particular_Host_Name.html" title="3.2.4. Clear a Particular Host Name" /><link rel="next" href="sec-Configuring_Host_Names_Using_nmcli.html" title="3.3. Configuring Host Names Using nmcli" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a access
key="p" href="sec_Clear_a_Particular_Host_Name.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Host_Names_Using_nmcli.html"><strong>Next</strong></a></li></ul><div class="section" id="sec_Changing_Host_Names_Remotely"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.5. Changing Host Names Remotely</h3></div></div></div><div class="para">
+ To execute a <code class="command">hostnamectl</code> command on a remote system, use the <code class="option">-H, --host</code> option as follows:
+<pre class="screen">~]# <code class="command">hostnamectl set-hostname <code class="option">-H</code> [<span class="optional"><em class="replaceable"><code>username</code></em></span>]@<em class="replaceable"><code>hostname</code></em></code></pre>
+ Where <em class="replaceable"><code>hostname</code></em> is the remote host you want to configure. The <em class="replaceable"><code>username</code></em> is optional. The <span class="application"><strong>hostnamectl</strong></span> tool will use <code class="systemitem">SSH</code> to connect to the remote system.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec_Clear_a_Particular_Host_Name.html"><strong>Prev</strong>3.2.4. Clear a Particular Host Name</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Host_Names_Using_nmcli.html"><strong>Next</strong>3.3. Configuring Host Names Using nmcli</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Clear_a_Particular_Host_Name.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Clear_a_Particular_Host_Name.html
new file mode 100644
index 0000000..1f568bb
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Clear_a_Particular_Host_Name.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.4. Clear a Particular Host Name</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec_Configuring_Host_Names_Using_hostnamectl.html" title="3.2. Configuring Host Names Using hostnamectl" /><link rel="prev" href="sec_Set_a_Particular_Host_Name.html" title="3.2.3. Set a Particular Host Name" /><link rel="next" href="sec_Changing_Host_Names_Remotely.html" title="3.2.5. Changing Host Names Remotely" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="
sec_Set_a_Particular_Host_Name.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec_Changing_Host_Names_Remotely.html"><strong>Next</strong></a></li></ul><div class="section" id="sec_Clear_a_Particular_Host_Name"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.4. Clear a Particular Host Name</h3></div></div></div><div class="para">
+ To clear a particular host name and allow it to revert to the default, enter the following command as <code class="systemitem">root</code> with the relevant option:
+<pre class="screen">~]# <code class="command">hostnamectl set-hostname <em class="replaceable"><code>""</code></em> [<span class="optional"><em class="replaceable"><code>option</code></em>...</span>]</code></pre>
+ Where <em class="replaceable"><code>""</code></em> is a quoted empty string and where <em class="replaceable"><code>option</code></em> is one or more of: <code class="option">--pretty</code>, <code class="option">--static</code>, and <code class="option">--transient</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec_Set_a_Particular_Host_Name.html"><strong>Prev</strong>3.2.3. Set a Particular Host Name</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec_Changing_Host_Names_Remotely.html"><strong>Next</strong>3.2.5. Changing Host Names Remotely</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Configuring_Host_Names_Using_hostnamectl.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Configuring_Host_Names_Using_hostnamectl.html
new file mode 100644
index 0000000..74536f6
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Configuring_Host_Names_Using_hostnamectl.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2. Configuring Host Names Using hostnamectl</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Configure_Host_Names.html" title="Chapter 3. Configure Host Names" /><link rel="prev" href="ch-Configure_Host_Names.html" title="Chapter 3. Configure Host Names" /><link rel="next" href="sec_Set_All_the_Host_Names.html" title="3.2.2. Set All the Host Names" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Configure_Host_Names.html"><strong>Prev</strong></a
></li><li class="next"><a accesskey="n" href="sec_Set_All_the_Host_Names.html"><strong>Next</strong></a></li></ul><div class="section" id="sec_Configuring_Host_Names_Using_hostnamectl"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.2. Configuring Host Names Using hostnamectl</h2></div></div></div><div class="para">
+ The <span class="application"><strong>hostnamectl</strong></span> tool is provided for administering the three separate classes of host names in use on a given system.
+ </div><div class="section" id="sec_View_All_the_Host_Names"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.1. View All the Host Names</h3></div></div></div><div class="para">
+ To view all the current host names, enter the following command:
+<pre class="screen">~]$ <code class="command">hostnamectl status</code></pre>
+ The <code class="option">status</code> option is implied by default if no option is given.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Configure_Host_Names.html"><strong>Prev</strong>Chapter 3. Configure Host Names</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec_Set_All_the_Host_Names.html"><strong>Next</strong>3.2.2. Set All the Host Names</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Set_All_the_Host_Names.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Set_All_the_Host_Names.html
new file mode 100644
index 0000000..01bbb97
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Set_All_the_Host_Names.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.2. Set All the Host Names</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec_Configuring_Host_Names_Using_hostnamectl.html" title="3.2. Configuring Host Names Using hostnamectl" /><link rel="prev" href="sec_Configuring_Host_Names_Using_hostnamectl.html" title="3.2. Configuring Host Names Using hostnamectl" /><link rel="next" href="sec_Set_a_Particular_Host_Name.html" title="3.2.3. Set a Particular Host Name" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><
a accesskey="p" href="sec_Configuring_Host_Names_Using_hostnamectl.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec_Set_a_Particular_Host_Name.html"><strong>Next</strong></a></li></ul><div class="section" id="sec_Set_All_the_Host_Names"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.2. Set All the Host Names</h3></div></div></div><div class="para">
+ To set all the host names on a system, enter the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">hostnamectl set-hostname <em class="replaceable"><code>name</code></em></code></pre>
+ This will alter the pretty, static, and transient host names alike. The static and transient host names will be simplified forms of the pretty host name. Spaces will be replaced with <span class="quote">“<span class="quote"><code class="literal">-</code></span>”</span> and special characters will be removed.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec_Configuring_Host_Names_Using_hostnamectl.html"><strong>Prev</strong>3.2. Configuring Host Names Using hostnamectl</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec_Set_a_Particular_Host_Name.html"><strong>Next</strong>3.2.3. Set a Particular Host Name</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Set_a_Particular_Host_Name.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Set_a_Particular_Host_Name.html
new file mode 100644
index 0000000..d040e39
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Set_a_Particular_Host_Name.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.3. Set a Particular Host Name</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="sec_Configuring_Host_Names_Using_hostnamectl.html" title="3.2. Configuring Host Names Using hostnamectl" /><link rel="prev" href="sec_Set_All_the_Host_Names.html" title="3.2.2. Set All the Host Names" /><link rel="next" href="sec_Clear_a_Particular_Host_Name.html" title="3.2.4. Clear a Particular Host Name" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec_Set_
All_the_Host_Names.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec_Clear_a_Particular_Host_Name.html"><strong>Next</strong></a></li></ul><div class="section" id="sec_Set_a_Particular_Host_Name"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.3. Set a Particular Host Name</h3></div></div></div><div class="para">
+ To set a particular host name, enter the following command as <code class="systemitem">root</code> with the relevant option:
+<pre class="screen">~]# <code class="command">hostnamectl set-hostname <em class="replaceable"><code>name</code></em> [<span class="optional"><em class="replaceable"><code>option</code></em>...</span>]</code></pre>
+ Where <em class="replaceable"><code>option</code></em> is one or more of: <code class="option">--pretty</code>, <code class="option">--static</code>, and <code class="option">--transient</code>.
+ </div><div class="para">
+ If the <code class="option">--static</code> or <code class="option">--transient</code> options are used together with the <code class="option">--pretty</code> option, the static and transient host names will be simplified forms of the pretty host name. Spaces will be replaced with <span class="quote">“<span class="quote"><code class="literal">-</code></span>”</span> and special characters will be removed. If the <code class="option">--pretty</code> option is not given, no simplification takes place.
+ </div><div class="para">
+ When setting a pretty host name, remember to use the appropriate quotation marks if the host name contains spaces or a single quotation mark. For example:
+<pre class="screen">~]# <code class="command">hostnamectl set-hostname "Stephen's notebook" --pretty</code></pre>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec_Set_All_the_Host_Names.html"><strong>Prev</strong>3.2.2. Set All the Host Names</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec_Clear_a_Particular_Host_Name.html"><strong>Next</strong>3.2.4. Clear a Particular Host Name</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Troubleshooting_Network_Device_Naming.html b/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Troubleshooting_Network_Device_Naming.html
new file mode 100644
index 0000000..e5d5cde
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/Networking_Guide/sec_Troubleshooting_Network_Device_Naming.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.10. Troubleshooting Network Device Naming</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Networking_Guide-21-en-US-2-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.Networking_Guide');
+ </script><link rel="home" href="index.html" title="Networking Guide" /><link rel="up" href="ch-Consistent_Network_Device_Naming.html" title="Chapter 8. Consistent Network Device Naming" /><link rel="prev" href="sec-Disabling_Consistent_Network_Device_Naming.html" title="8.9. Disabling Consistent Network Device Naming" /><link rel="next" href="sec-Consistent_Network_Device_Naming-additional_resources.html" title="8.11. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li clas
s="previous"><a accesskey="p" href="sec-Disabling_Consistent_Network_Device_Naming.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Consistent_Network_Device_Naming-additional_resources.html"><strong>Next</strong></a></li></ul><div class="section" id="sec_Troubleshooting_Network_Device_Naming"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.10. Troubleshooting Network Device Naming</h2></div></div></div><div class="para">
+ Predictable interface names will be assigned for each interface, if applicable, as per the procedure described in <a class="xref" href="sec-Understanding_the_Device_Renaming_Procedure.html">Section 8.2, “Understanding the Device Renaming Procedure”</a>. To view the list of possible names <span class="application"><strong>udev</strong></span> will use, issue a command in the following form as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">udevadm info /sys/class/net/<em class="replaceable"><code>ifname</code></em> | grep ID_NET_NAME</code></pre>
+ where <em class="replaceable"><code>ifname</code></em> is one of the interfaces listed by the following command:
+<pre class="screen">~]$ <code class="command">ls /sys/class/net/</code></pre>
+
+ </div><div class="para">
+ One of the possible names will be applied by <span class="application"><strong>udev</strong></span> according to the rules as described in <a class="xref" href="sec-Understanding_the_Device_Renaming_Procedure.html">Section 8.2, “Understanding the Device Renaming Procedure”</a>, and summarized here:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/lib/udev/rules.d/60-net.rules</code> - from initscripts,
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/lib/udev/rules.d/71-biosdevname.rules</code> - from <span class="application"><strong>biosdevname</strong></span>,
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/lib/udev/rules.d/80-net-name-slot.rules</code> - from <code class="systemitem">systemd</code>
+ </div></li></ul></div>
+
+ </div><div class="para">
+ From the above list of rule files it can be seen that if interface naming is done via initscripts or <span class="application"><strong>biosdevname</strong></span> it always takes precedence over <span class="application"><strong>udev</strong></span> native naming. However if initscripts renaming is not taking place and <span class="application"><strong>biosdevname</strong></span> is disabled, then to alter the interface names copy the <code class="filename">80-net-name-slot.rules</code> from <code class="filename">/usr/</code> to <code class="filename">/etc/</code> and edit the file appropriately. In other words, comment out or arrange schemes to be used in a certain order.
+ </div><div class="example" id="ex-Some_interfaces_have_names_from_the_kernel_namespace_while_others_are_successfully_renamed_by_udev"><h6>Example 8.1. Some interfaces have names from the kernel namespace (eth[0,1,2...]) while others are successfully renamed by udev</h6><div class="example-contents"><div class="para">
+ Mixed up schemes most likely means that either for some hardware there is no usable information provided by the kernel to <span class="application"><strong>udev</strong></span>, thus it could not figure out any names, or the information provided to <span class="application"><strong>udev</strong></span> is not suitable, for example non-unique device IDs. The latter is more common and the solution is to use a custom naming scheme in ifcfg files or alter which <span class="application"><strong>udev</strong></span> scheme is in use by editing 80-net-name-slot.rules.
+ </div></div></div><br class="example-break" /><div class="example" id="ex-In_var-log-messages_or_the_systemd_journal_renaming_is_seen_to_be_done_twice_for_each_interface"><h6>Example 8.2. In /var/log/messages or the systemd journal, renaming is seen to be done twice for each interface</h6><div class="example-contents"><div class="para">
+ Systems with the naming scheme encoded in ifcfg files but which do not have a regenerated <code class="systemitem">initrd</code> image are likely to encounter this issue. The interface name is initially assigned (via <span class="application"><strong>biosdevname</strong></span> or <span class="application"><strong>udev</strong></span> or dracut parameters on the kernel command line) during early-boot while still in <code class="systemitem">initrd</code>. Then after switching to real <code class="systemitem">rootfs</code>, renaming is done a second time and a new interface name is determined by the <code class="filename">/usr/lib/udev/rename_device</code> binary spawned by <span class="application"><strong>udev</strong></span> because of processing 60-net.rules. You can safely ignore such messages.
+ </div></div></div><br class="example-break" /><div class="example" id="ex-Using_naming_scheme_in_ifcfg_files_with_ethX_names_does_not_work"><h6>Example 8.3. Using naming scheme in ifcfg files with ethX names does not work</h6><div class="example-contents"><div class="para">
+ Use of interface names from kernel namespace is discouraged. To get predictable and stable interface names please use some other prefix than "eth".
+ </div></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Disabling_Consistent_Network_Device_Naming.html"><strong>Prev</strong>8.9. Disabling Consistent Network Device Naming</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Consistent_Network_Device_Naming-additional_resources.html"><strong>Next</strong>8.11. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf b/public_html/en-US/Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf
new file mode 100644
index 0000000..07b5d4f
Binary files /dev/null and b/public_html/en-US/Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf differ
diff --git a/public_html/en-US/Site_Statistics.html b/public_html/en-US/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/en-US/Site_Statistics.html
+++ b/public_html/en-US/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/en-US/opds-Community_Services_Infrastructure.xml b/public_html/en-US/opds-Community_Services_Infrastructure.xml
index 8a4923c..de67b4a 100644
--- a/public_html/en-US/opds-Community_Services_Infrastructure.xml
+++ b/public_html/en-US/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora.xml b/public_html/en-US/opds-Fedora.xml
index fdbe634..fd217bd 100644
--- a/public_html/en-US/opds-Fedora.xml
+++ b/public_html/en-US/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>en-US</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/en-US/opds-Fedora_Contributor_Documentation.xml b/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
index 6d58871..ce70ae2 100644
--- a/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Core.xml b/public_html/en-US/opds-Fedora_Core.xml
index 55b7abf..13c0115 100644
--- a/public_html/en-US/opds-Fedora_Core.xml
+++ b/public_html/en-US/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Documentation.xml b/public_html/en-US/opds-Fedora_Documentation.xml
index 8a42b9c..2e92a76 100644
--- a/public_html/en-US/opds-Fedora_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Draft_Documentation.xml b/public_html/en-US/opds-Fedora_Draft_Documentation.xml
index 9724afb..074c631 100644
--- a/public_html/en-US/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Security_Team.xml b/public_html/en-US/opds-Fedora_Security_Team.xml
index 90fa4a7..680b856 100644
--- a/public_html/en-US/opds-Fedora_Security_Team.xml
+++ b/public_html/en-US/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds.xml b/public_html/en-US/opds.xml
index af949e5..e48d10d 100644
--- a/public_html/en-US/opds.xml
+++ b/public_html/en-US/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/en-US/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/en-US/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/en-US/toc.html b/public_html/en-US/toc.html
index 1f6a7f9..628f4f5 100644
--- a/public_html/en-US/toc.html
+++ b/public_html/en-US/toc.html
@@ -107,6 +107,15 @@
<a class="type" href="./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed">
+ <a class="type" href="Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='./Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types" onclick="work=0;">
+ <a class="type" href="./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed">
<a class="type" href="Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='./Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types" onclick="work=0;">
diff --git a/public_html/es-ES/Site_Statistics.html b/public_html/es-ES/Site_Statistics.html
index 9df165b..645f4ad 100644
--- a/public_html/es-ES/Site_Statistics.html
+++ b/public_html/es-ES/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Idiomas totales: </b>45<br />
- <b>Paquetes totales: </b>917
+ <b>Paquetes totales: </b>918
</div>
</body>
</html>
diff --git a/public_html/es-ES/opds-Community_Services_Infrastructure.xml b/public_html/es-ES/opds-Community_Services_Infrastructure.xml
index 9a31bbf..fc1fe5c 100644
--- a/public_html/es-ES/opds-Community_Services_Infrastructure.xml
+++ b/public_html/es-ES/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora.xml b/public_html/es-ES/opds-Fedora.xml
index de96917..94d2dde 100644
--- a/public_html/es-ES/opds-Fedora.xml
+++ b/public_html/es-ES/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>es-ES</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Notas de lanzamiento</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-es-ES.epub</id>
<!--author>
diff --git a/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml b/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
index c04c474..e6ab264 100644
--- a/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Documentación de Contribuyente</title>
<subtitle>Fedora Documentación de Contribuyente</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Core.xml b/public_html/es-ES/opds-Fedora_Core.xml
index b99b20c..bf100e5 100644
--- a/public_html/es-ES/opds-Fedora_Core.xml
+++ b/public_html/es-ES/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Documentation.xml b/public_html/es-ES/opds-Fedora_Documentation.xml
index 9dde423..8c6797b 100644
--- a/public_html/es-ES/opds-Fedora_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Draft_Documentation.xml b/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
index b272ca2..e9d3fe8 100644
--- a/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Security_Team.xml b/public_html/es-ES/opds-Fedora_Security_Team.xml
index 31e9267..298046c 100644
--- a/public_html/es-ES/opds-Fedora_Security_Team.xml
+++ b/public_html/es-ES/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds.xml b/public_html/es-ES/opds.xml
index 9843d37..89332f7 100644
--- a/public_html/es-ES/opds.xml
+++ b/public_html/es-ES/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/es-ES/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/es-ES/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Documentación de Contribuyente</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/es-ES/toc.html b/public_html/es-ES/toc.html
index 7738e6c..b61c7dc 100644
--- a/public_html/es-ES/toc.html
+++ b/public_html/es-ES/toc.html
@@ -124,6 +124,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Security-Enhanced_Linux' class="book collapsed" onclick="toggle(event, 'Fedora.21.Security-Enhanced_Linux.types');">
<a class="type" href="../en-US/Fedora/21/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Security-Enhanced_Linux/index.html'"><span class="book">Security-Enhanced Linux</span></a>
<div id='Fedora.21.Security-Enhanced_Linux.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/fa-IR/Site_Statistics.html b/public_html/fa-IR/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/fa-IR/Site_Statistics.html
+++ b/public_html/fa-IR/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/fa-IR/opds-Community_Services_Infrastructure.xml b/public_html/fa-IR/opds-Community_Services_Infrastructure.xml
index 7486ab3..becbe80 100644
--- a/public_html/fa-IR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/fa-IR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora.xml b/public_html/fa-IR/opds-Fedora.xml
index 5bb760b..342a530 100644
--- a/public_html/fa-IR/opds-Fedora.xml
+++ b/public_html/fa-IR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>fa-IR</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml b/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
index 433dfb2..191e7f6 100644
--- a/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Contributor_Documentation.xml</id>
<title>مستندات مشارکت کننده فدورا</title>
<subtitle>مستندات مشارکت کننده فدورا</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Core.xml b/public_html/fa-IR/opds-Fedora_Core.xml
index adc87b5..a13810c 100644
--- a/public_html/fa-IR/opds-Fedora_Core.xml
+++ b/public_html/fa-IR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Documentation.xml b/public_html/fa-IR/opds-Fedora_Documentation.xml
index 100d6c5..8a045b0 100644
--- a/public_html/fa-IR/opds-Fedora_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml b/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
index 123e24c..fa48839 100644
--- a/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Security_Team.xml b/public_html/fa-IR/opds-Fedora_Security_Team.xml
index ff543d8..7d1a6ff 100644
--- a/public_html/fa-IR/opds-Fedora_Security_Team.xml
+++ b/public_html/fa-IR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds.xml b/public_html/fa-IR/opds.xml
index 2495c9e..9442976 100644
--- a/public_html/fa-IR/opds.xml
+++ b/public_html/fa-IR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/fa-IR/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/fa-IR/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>مستندات مشارکت کننده فدورا</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/fa-IR/toc.html b/public_html/fa-IR/toc.html
index 70ec4f7..9f5ab29 100644
--- a/public_html/fa-IR/toc.html
+++ b/public_html/fa-IR/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/fi-FI/Site_Statistics.html b/public_html/fi-FI/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/fi-FI/Site_Statistics.html
+++ b/public_html/fi-FI/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/fi-FI/opds-Community_Services_Infrastructure.xml b/public_html/fi-FI/opds-Community_Services_Infrastructure.xml
index f271be9..f30f42b 100644
--- a/public_html/fi-FI/opds-Community_Services_Infrastructure.xml
+++ b/public_html/fi-FI/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora.xml b/public_html/fi-FI/opds-Fedora.xml
index 79a6b1d..e335d50 100644
--- a/public_html/fi-FI/opds-Fedora.xml
+++ b/public_html/fi-FI/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>fi-FI</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml b/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
index 6815639..50aa3ba 100644
--- a/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Core.xml b/public_html/fi-FI/opds-Fedora_Core.xml
index f6b59e9..1a691f1 100644
--- a/public_html/fi-FI/opds-Fedora_Core.xml
+++ b/public_html/fi-FI/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Documentation.xml b/public_html/fi-FI/opds-Fedora_Documentation.xml
index efafe49..d3001d7 100644
--- a/public_html/fi-FI/opds-Fedora_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml b/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
index 3c1e4c9..d8d883ba 100644
--- a/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Security_Team.xml b/public_html/fi-FI/opds-Fedora_Security_Team.xml
index 7ab5d1d..f6d1d62 100644
--- a/public_html/fi-FI/opds-Fedora_Security_Team.xml
+++ b/public_html/fi-FI/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds.xml b/public_html/fi-FI/opds.xml
index 6a43678..7a73100 100644
--- a/public_html/fi-FI/opds.xml
+++ b/public_html/fi-FI/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/fi-FI/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/fi-FI/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/fi-FI/toc.html b/public_html/fi-FI/toc.html
index 8a5f1a8..498fb34 100644
--- a/public_html/fi-FI/toc.html
+++ b/public_html/fi-FI/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/fr-FR/Site_Statistics.html b/public_html/fr-FR/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/fr-FR/Site_Statistics.html
+++ b/public_html/fr-FR/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/fr-FR/opds-Community_Services_Infrastructure.xml b/public_html/fr-FR/opds-Community_Services_Infrastructure.xml
index d9f0c04..9c4eb5c 100644
--- a/public_html/fr-FR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/fr-FR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora.xml b/public_html/fr-FR/opds-Fedora.xml
index 17b6390..8c0b359 100644
--- a/public_html/fr-FR/opds-Fedora.xml
+++ b/public_html/fr-FR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>fr-FR</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml b/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
index 197b3fc..e992ec6 100644
--- a/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Core.xml b/public_html/fr-FR/opds-Fedora_Core.xml
index 41a181a..03f9065 100644
--- a/public_html/fr-FR/opds-Fedora_Core.xml
+++ b/public_html/fr-FR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Documentation.xml b/public_html/fr-FR/opds-Fedora_Documentation.xml
index 09eb65d..a044974 100644
--- a/public_html/fr-FR/opds-Fedora_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml b/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
index f3dd0c8..481bc07 100644
--- a/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Security_Team.xml b/public_html/fr-FR/opds-Fedora_Security_Team.xml
index e1cabe1..93e95e3 100644
--- a/public_html/fr-FR/opds-Fedora_Security_Team.xml
+++ b/public_html/fr-FR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds.xml b/public_html/fr-FR/opds.xml
index 884245d..6a175d7 100644
--- a/public_html/fr-FR/opds.xml
+++ b/public_html/fr-FR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/fr-FR/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/fr-FR/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/fr-FR/toc.html b/public_html/fr-FR/toc.html
index 4559cfc..7fcfb07 100644
--- a/public_html/fr-FR/toc.html
+++ b/public_html/fr-FR/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/gu-IN/Site_Statistics.html b/public_html/gu-IN/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/gu-IN/Site_Statistics.html
+++ b/public_html/gu-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/gu-IN/opds-Community_Services_Infrastructure.xml b/public_html/gu-IN/opds-Community_Services_Infrastructure.xml
index 8c2db31..59e4797 100644
--- a/public_html/gu-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/gu-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora.xml b/public_html/gu-IN/opds-Fedora.xml
index 25b90dc..a51169b 100644
--- a/public_html/gu-IN/opds-Fedora.xml
+++ b/public_html/gu-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>gu-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
index fdc7729..89266fa 100644
--- a/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Core.xml b/public_html/gu-IN/opds-Fedora_Core.xml
index dc32dfa..82ea884 100644
--- a/public_html/gu-IN/opds-Fedora_Core.xml
+++ b/public_html/gu-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Documentation.xml b/public_html/gu-IN/opds-Fedora_Documentation.xml
index 9ee4634..94cff42 100644
--- a/public_html/gu-IN/opds-Fedora_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml b/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
index 1504312..d27555b 100644
--- a/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Security_Team.xml b/public_html/gu-IN/opds-Fedora_Security_Team.xml
index 848f51f..a284c77 100644
--- a/public_html/gu-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/gu-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds.xml b/public_html/gu-IN/opds.xml
index 9f0b45d..c0f8087 100644
--- a/public_html/gu-IN/opds.xml
+++ b/public_html/gu-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/gu-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/gu-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/gu-IN/toc.html b/public_html/gu-IN/toc.html
index 812edb3..08e3461 100644
--- a/public_html/gu-IN/toc.html
+++ b/public_html/gu-IN/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/he-IL/Site_Statistics.html b/public_html/he-IL/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/he-IL/Site_Statistics.html
+++ b/public_html/he-IL/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/he-IL/opds-Community_Services_Infrastructure.xml b/public_html/he-IL/opds-Community_Services_Infrastructure.xml
index 20c647b..6c6191e 100644
--- a/public_html/he-IL/opds-Community_Services_Infrastructure.xml
+++ b/public_html/he-IL/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora.xml b/public_html/he-IL/opds-Fedora.xml
index 96ed264..98eaa0d 100644
--- a/public_html/he-IL/opds-Fedora.xml
+++ b/public_html/he-IL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>he-IL</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml b/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
index 761f0c4..393deb5 100644
--- a/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Core.xml b/public_html/he-IL/opds-Fedora_Core.xml
index 5176d76..510c78a 100644
--- a/public_html/he-IL/opds-Fedora_Core.xml
+++ b/public_html/he-IL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Documentation.xml b/public_html/he-IL/opds-Fedora_Documentation.xml
index b3225f5..048ebc5 100644
--- a/public_html/he-IL/opds-Fedora_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Draft_Documentation.xml b/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
index 3acc28e..0a09c1a 100644
--- a/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Security_Team.xml b/public_html/he-IL/opds-Fedora_Security_Team.xml
index cd8adb2..e24b3b4 100644
--- a/public_html/he-IL/opds-Fedora_Security_Team.xml
+++ b/public_html/he-IL/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds.xml b/public_html/he-IL/opds.xml
index 8d7604c..9872890 100644
--- a/public_html/he-IL/opds.xml
+++ b/public_html/he-IL/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/he-IL/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/he-IL/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/he-IL/toc.html b/public_html/he-IL/toc.html
index 5372527..26f4a7a 100644
--- a/public_html/he-IL/toc.html
+++ b/public_html/he-IL/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/hi-IN/Site_Statistics.html b/public_html/hi-IN/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/hi-IN/Site_Statistics.html
+++ b/public_html/hi-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/hi-IN/opds-Community_Services_Infrastructure.xml b/public_html/hi-IN/opds-Community_Services_Infrastructure.xml
index 2153433..8b11667 100644
--- a/public_html/hi-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/hi-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora.xml b/public_html/hi-IN/opds-Fedora.xml
index 90b8e7c..a165b81 100644
--- a/public_html/hi-IN/opds-Fedora.xml
+++ b/public_html/hi-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>hi-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
index 2706b31..bac93b0 100644
--- a/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Core.xml b/public_html/hi-IN/opds-Fedora_Core.xml
index 0add1b2..456ff72 100644
--- a/public_html/hi-IN/opds-Fedora_Core.xml
+++ b/public_html/hi-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Documentation.xml b/public_html/hi-IN/opds-Fedora_Documentation.xml
index 9508881..850aef8 100644
--- a/public_html/hi-IN/opds-Fedora_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml b/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
index bc4ecd8..d03d29c 100644
--- a/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Security_Team.xml b/public_html/hi-IN/opds-Fedora_Security_Team.xml
index 2b2c08d..b8166d9 100644
--- a/public_html/hi-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/hi-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds.xml b/public_html/hi-IN/opds.xml
index e17f66d..007ca59 100644
--- a/public_html/hi-IN/opds.xml
+++ b/public_html/hi-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/hi-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/hi-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/hi-IN/toc.html b/public_html/hi-IN/toc.html
index 1ac968e..d58a3f5 100644
--- a/public_html/hi-IN/toc.html
+++ b/public_html/hi-IN/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/hu-HU/Site_Statistics.html b/public_html/hu-HU/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/hu-HU/Site_Statistics.html
+++ b/public_html/hu-HU/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/hu-HU/opds-Community_Services_Infrastructure.xml b/public_html/hu-HU/opds-Community_Services_Infrastructure.xml
index d773836..e1f7e7e 100644
--- a/public_html/hu-HU/opds-Community_Services_Infrastructure.xml
+++ b/public_html/hu-HU/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora.xml b/public_html/hu-HU/opds-Fedora.xml
index d94ab63..1d502d5 100644
--- a/public_html/hu-HU/opds-Fedora.xml
+++ b/public_html/hu-HU/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>hu-HU</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml b/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
index b3c0b30..c3cdbcd 100644
--- a/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Core.xml b/public_html/hu-HU/opds-Fedora_Core.xml
index 7df7f64..2a97259 100644
--- a/public_html/hu-HU/opds-Fedora_Core.xml
+++ b/public_html/hu-HU/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Documentation.xml b/public_html/hu-HU/opds-Fedora_Documentation.xml
index e8cb140..4e5a6a5 100644
--- a/public_html/hu-HU/opds-Fedora_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml b/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
index 47204b8..ddd06ed 100644
--- a/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Security_Team.xml b/public_html/hu-HU/opds-Fedora_Security_Team.xml
index 850721d..72ac990 100644
--- a/public_html/hu-HU/opds-Fedora_Security_Team.xml
+++ b/public_html/hu-HU/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds.xml b/public_html/hu-HU/opds.xml
index 84c8c21..2e4d391 100644
--- a/public_html/hu-HU/opds.xml
+++ b/public_html/hu-HU/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/hu-HU/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/hu-HU/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/hu-HU/toc.html b/public_html/hu-HU/toc.html
index 6126946..928cd45 100644
--- a/public_html/hu-HU/toc.html
+++ b/public_html/hu-HU/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/ia/Site_Statistics.html b/public_html/ia/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/ia/Site_Statistics.html
+++ b/public_html/ia/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/ia/opds-Community_Services_Infrastructure.xml b/public_html/ia/opds-Community_Services_Infrastructure.xml
index 263b460..bdb46c8 100644
--- a/public_html/ia/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ia/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora.xml b/public_html/ia/opds-Fedora.xml
index 774b82f..561ccd0 100644
--- a/public_html/ia/opds-Fedora.xml
+++ b/public_html/ia/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>ia</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/ia/opds-Fedora_Contributor_Documentation.xml b/public_html/ia/opds-Fedora_Contributor_Documentation.xml
index 7a2fc46..6256d11 100644
--- a/public_html/ia/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ia/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora_Core.xml b/public_html/ia/opds-Fedora_Core.xml
index 700ce8f..2f5de17 100644
--- a/public_html/ia/opds-Fedora_Core.xml
+++ b/public_html/ia/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora_Documentation.xml b/public_html/ia/opds-Fedora_Documentation.xml
index 8d4e67f..506818e 100644
--- a/public_html/ia/opds-Fedora_Documentation.xml
+++ b/public_html/ia/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora_Draft_Documentation.xml b/public_html/ia/opds-Fedora_Draft_Documentation.xml
index 84ece9c..5efad0b 100644
--- a/public_html/ia/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ia/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora_Security_Team.xml b/public_html/ia/opds-Fedora_Security_Team.xml
index 1d7f45f..11b5686 100644
--- a/public_html/ia/opds-Fedora_Security_Team.xml
+++ b/public_html/ia/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds.xml b/public_html/ia/opds.xml
index ff3bdcc..219948b 100644
--- a/public_html/ia/opds.xml
+++ b/public_html/ia/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ia/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ia/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ia/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ia/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ia/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ia/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ia/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ia/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ia/toc.html b/public_html/ia/toc.html
index 028157f..ece62fd 100644
--- a/public_html/ia/toc.html
+++ b/public_html/ia/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/id-ID/Site_Statistics.html b/public_html/id-ID/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/id-ID/Site_Statistics.html
+++ b/public_html/id-ID/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/id-ID/opds-Community_Services_Infrastructure.xml b/public_html/id-ID/opds-Community_Services_Infrastructure.xml
index 343def0..33e8bda 100644
--- a/public_html/id-ID/opds-Community_Services_Infrastructure.xml
+++ b/public_html/id-ID/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora.xml b/public_html/id-ID/opds-Fedora.xml
index 23d36c5..5ae88e2 100644
--- a/public_html/id-ID/opds-Fedora.xml
+++ b/public_html/id-ID/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>id-ID</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml b/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
index 02e7a09..241a348 100644
--- a/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Core.xml b/public_html/id-ID/opds-Fedora_Core.xml
index c8aae7a..cfe5e7f 100644
--- a/public_html/id-ID/opds-Fedora_Core.xml
+++ b/public_html/id-ID/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Documentation.xml b/public_html/id-ID/opds-Fedora_Documentation.xml
index 57c4b93..84a890e 100644
--- a/public_html/id-ID/opds-Fedora_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Draft_Documentation.xml b/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
index 1c7863c..56d4f7d 100644
--- a/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Security_Team.xml b/public_html/id-ID/opds-Fedora_Security_Team.xml
index 2fef0f2..82d8d5e 100644
--- a/public_html/id-ID/opds-Fedora_Security_Team.xml
+++ b/public_html/id-ID/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds.xml b/public_html/id-ID/opds.xml
index 08a78aa..d963745 100644
--- a/public_html/id-ID/opds.xml
+++ b/public_html/id-ID/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/id-ID/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/id-ID/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/id-ID/toc.html b/public_html/id-ID/toc.html
index c9146ca..4786832 100644
--- a/public_html/id-ID/toc.html
+++ b/public_html/id-ID/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/index.html b/public_html/index.html
index 9100bfd..039a9d2 100644
--- a/public_html/index.html
+++ b/public_html/index.html
@@ -16,7 +16,7 @@
lang = window.navigator.language;
var match = 0;
- var locales = ["as-IN","bg-BG","bn-IN","bs-BA","ca-ES","cs-CZ","da-DK","de-DE","el-GR","en-US","es-ES","fa-IR","fi-FI","fr-FR","gu-IN","he-IL","hi-IN","hu-HU","ia","id-ID","it-IT","ja-JP","kn-IN","ko-KR","lt-LT","ml-IN","mr-IN","nb-NO","nl-NL","or-IN","pa-IN","pl-PL","pt-BR","pt-PT","ro","ru-RU","sk-SK","sr-Latn-RS","sr-RS","sv-SE","ta-IN","te-IN","uk-UA","zh-CN","zh-TW"];
+ var locales = ["as-IN","bg-BG","bn-IN","bs-BA","ca-ES","cs-CZ","da-DK","de-DE","el-GR","en-US","es-ES","fa-IR","fi-FI","fr-FR","gu-IN","he-IL","hi-IN","hu-HU","ia","id-ID","it-IT","ja-JP","kn-IN","ko-KR","lt-LT","ml-IN","mr-IN","nb-NO","nl-NL","or-IN","pa-IN","pl-PL","pt-BR","pt-PT","ro-RO","ru-RU","sk-SK","sr-Latn-RS","sr-RS","sv-SE","ta-IN","te-IN","uk-UA","zh-CN","zh-TW"];
if(lang) {
// Try for full match of lang_LOC
diff --git a/public_html/it-IT/Site_Statistics.html b/public_html/it-IT/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/it-IT/Site_Statistics.html
+++ b/public_html/it-IT/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/it-IT/opds-Community_Services_Infrastructure.xml b/public_html/it-IT/opds-Community_Services_Infrastructure.xml
index 41db89f..b753e67 100644
--- a/public_html/it-IT/opds-Community_Services_Infrastructure.xml
+++ b/public_html/it-IT/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora.xml b/public_html/it-IT/opds-Fedora.xml
index 14fa9df..7f32d31 100644
--- a/public_html/it-IT/opds-Fedora.xml
+++ b/public_html/it-IT/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>it-IT</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Note di rilascio</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-it-IT.epub</id>
<!--author>
diff --git a/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml b/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
index 0c30cc2..e994687 100644
--- a/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Contributor_Documentation.xml</id>
<title>Documentazione Collaboratori Fedora</title>
<subtitle>Documentazione Collaboratori Fedora</subtitle>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Core.xml b/public_html/it-IT/opds-Fedora_Core.xml
index bd3143a..a0a6566 100644
--- a/public_html/it-IT/opds-Fedora_Core.xml
+++ b/public_html/it-IT/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Documentation.xml b/public_html/it-IT/opds-Fedora_Documentation.xml
index 3db6507..eed6fd0 100644
--- a/public_html/it-IT/opds-Fedora_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Draft_Documentation.xml b/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
index 9525c4a..ddc5d18 100644
--- a/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Security_Team.xml b/public_html/it-IT/opds-Fedora_Security_Team.xml
index e50969c..d28679c 100644
--- a/public_html/it-IT/opds-Fedora_Security_Team.xml
+++ b/public_html/it-IT/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds.xml b/public_html/it-IT/opds.xml
index db88ab7..14f8d06 100644
--- a/public_html/it-IT/opds.xml
+++ b/public_html/it-IT/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/it-IT/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/it-IT/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Documentazione Collaboratori Fedora</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/it-IT/toc.html b/public_html/it-IT/toc.html
index efa9dbf..7aee655 100644
--- a/public_html/it-IT/toc.html
+++ b/public_html/it-IT/toc.html
@@ -124,6 +124,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Security-Enhanced_Linux' class="book collapsed" onclick="toggle(event, 'Fedora.21.Security-Enhanced_Linux.types');">
<a class="type" href="../en-US/Fedora/21/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Security-Enhanced_Linux/index.html'"><span class="book">Security-Enhanced Linux</span></a>
<div id='Fedora.21.Security-Enhanced_Linux.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/ja-JP/Site_Statistics.html b/public_html/ja-JP/Site_Statistics.html
index a07b12e..e949835 100644
--- a/public_html/ja-JP/Site_Statistics.html
+++ b/public_html/ja-JP/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>言語数の合計: </b>45<br />
- <b>パッケージ数の合計: </b>917
+ <b>パッケージ数の合計: </b>918
</div>
</body>
</html>
diff --git a/public_html/ja-JP/opds-Community_Services_Infrastructure.xml b/public_html/ja-JP/opds-Community_Services_Infrastructure.xml
index c2a770b..858b575 100644
--- a/public_html/ja-JP/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ja-JP/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora.xml b/public_html/ja-JP/opds-Fedora.xml
index 4aeba604d..1668289 100644
--- a/public_html/ja-JP/opds-Fedora.xml
+++ b/public_html/ja-JP/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>ja-JP</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
index c95ef16..90ebfd1 100644
--- a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora コントリビュータ用ドキュメント</title>
<subtitle>Fedora コントリビュータ用ドキュメント</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Core.xml b/public_html/ja-JP/opds-Fedora_Core.xml
index 99ef366..29c5b1c 100644
--- a/public_html/ja-JP/opds-Fedora_Core.xml
+++ b/public_html/ja-JP/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Documentation.xml b/public_html/ja-JP/opds-Fedora_Documentation.xml
index 243a9cf..c0e8673 100644
--- a/public_html/ja-JP/opds-Fedora_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml b/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
index a88dbfa..ca1a65d 100644
--- a/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Security_Team.xml b/public_html/ja-JP/opds-Fedora_Security_Team.xml
index dc606f4..0d64eb6 100644
--- a/public_html/ja-JP/opds-Fedora_Security_Team.xml
+++ b/public_html/ja-JP/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds.xml b/public_html/ja-JP/opds.xml
index bae49c8..0459619 100644
--- a/public_html/ja-JP/opds.xml
+++ b/public_html/ja-JP/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ja-JP/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ja-JP/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora コントリビュータ用ドキュメント</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ja-JP/toc.html b/public_html/ja-JP/toc.html
index 36bd0f9..1f5f30b 100644
--- a/public_html/ja-JP/toc.html
+++ b/public_html/ja-JP/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/kn-IN/Site_Statistics.html b/public_html/kn-IN/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/kn-IN/Site_Statistics.html
+++ b/public_html/kn-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/kn-IN/opds-Community_Services_Infrastructure.xml b/public_html/kn-IN/opds-Community_Services_Infrastructure.xml
index e5fdd9b..b6a7608 100644
--- a/public_html/kn-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/kn-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora.xml b/public_html/kn-IN/opds-Fedora.xml
index 076c16d..e2ab215 100644
--- a/public_html/kn-IN/opds-Fedora.xml
+++ b/public_html/kn-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>kn-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
index 9b2eb37..9ce70e1 100644
--- a/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Core.xml b/public_html/kn-IN/opds-Fedora_Core.xml
index aa224ec..b6268c2 100644
--- a/public_html/kn-IN/opds-Fedora_Core.xml
+++ b/public_html/kn-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Documentation.xml b/public_html/kn-IN/opds-Fedora_Documentation.xml
index 372ab20..fb3eb86 100644
--- a/public_html/kn-IN/opds-Fedora_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml b/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
index 60d043b..b80cf48 100644
--- a/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Security_Team.xml b/public_html/kn-IN/opds-Fedora_Security_Team.xml
index 1753549..813a31e 100644
--- a/public_html/kn-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/kn-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds.xml b/public_html/kn-IN/opds.xml
index 9a89e1c..e89af5b 100644
--- a/public_html/kn-IN/opds.xml
+++ b/public_html/kn-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/kn-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/kn-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/kn-IN/toc.html b/public_html/kn-IN/toc.html
index 1b2289f..5ce38d5 100644
--- a/public_html/kn-IN/toc.html
+++ b/public_html/kn-IN/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/ko-KR/Site_Statistics.html b/public_html/ko-KR/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/ko-KR/Site_Statistics.html
+++ b/public_html/ko-KR/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/ko-KR/opds-Community_Services_Infrastructure.xml b/public_html/ko-KR/opds-Community_Services_Infrastructure.xml
index b40e349..d205df9 100644
--- a/public_html/ko-KR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ko-KR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora.xml b/public_html/ko-KR/opds-Fedora.xml
index a93e796..fe1ca46 100644
--- a/public_html/ko-KR/opds-Fedora.xml
+++ b/public_html/ko-KR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>ko-KR</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml b/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
index 3b9235d..70ce43c 100644
--- a/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Core.xml b/public_html/ko-KR/opds-Fedora_Core.xml
index e9c1510..14eefef 100644
--- a/public_html/ko-KR/opds-Fedora_Core.xml
+++ b/public_html/ko-KR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Documentation.xml b/public_html/ko-KR/opds-Fedora_Documentation.xml
index 592922d..a51341e 100644
--- a/public_html/ko-KR/opds-Fedora_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml b/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
index 1cdea4c..4a0cf0d 100644
--- a/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Security_Team.xml b/public_html/ko-KR/opds-Fedora_Security_Team.xml
index 492c16f..059e3e1 100644
--- a/public_html/ko-KR/opds-Fedora_Security_Team.xml
+++ b/public_html/ko-KR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds.xml b/public_html/ko-KR/opds.xml
index 3e06f5d..1170aac 100644
--- a/public_html/ko-KR/opds.xml
+++ b/public_html/ko-KR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ko-KR/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ko-KR/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ko-KR/toc.html b/public_html/ko-KR/toc.html
index 2371ade..4563d64 100644
--- a/public_html/ko-KR/toc.html
+++ b/public_html/ko-KR/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/lt-LT/Site_Statistics.html b/public_html/lt-LT/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/lt-LT/Site_Statistics.html
+++ b/public_html/lt-LT/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/lt-LT/opds-Community_Services_Infrastructure.xml b/public_html/lt-LT/opds-Community_Services_Infrastructure.xml
index 996dfec..6e69b6d 100644
--- a/public_html/lt-LT/opds-Community_Services_Infrastructure.xml
+++ b/public_html/lt-LT/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/lt-LT/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds-Fedora.xml b/public_html/lt-LT/opds-Fedora.xml
index 3b89773..b165ff1 100644
--- a/public_html/lt-LT/opds-Fedora.xml
+++ b/public_html/lt-LT/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/lt-LT/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>lt-LT</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Leidimo naujienos</title>
<id>http://docs.fedoraproject.org/lt-LT/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-lt-LT.epub</id>
<!--author>
diff --git a/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml b/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml
index ae7cc1d..716a974 100644
--- a/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/lt-LT/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds-Fedora_Core.xml b/public_html/lt-LT/opds-Fedora_Core.xml
index 3829f5c..f0429d1 100644
--- a/public_html/lt-LT/opds-Fedora_Core.xml
+++ b/public_html/lt-LT/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/lt-LT/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds-Fedora_Documentation.xml b/public_html/lt-LT/opds-Fedora_Documentation.xml
index 4fd8e2f..8994fe2 100644
--- a/public_html/lt-LT/opds-Fedora_Documentation.xml
+++ b/public_html/lt-LT/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/lt-LT/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds-Fedora_Draft_Documentation.xml b/public_html/lt-LT/opds-Fedora_Draft_Documentation.xml
index c09b930..59ed4b6 100644
--- a/public_html/lt-LT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/lt-LT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/lt-LT/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds-Fedora_Security_Team.xml b/public_html/lt-LT/opds-Fedora_Security_Team.xml
index 2037cf7..87fe80a 100644
--- a/public_html/lt-LT/opds-Fedora_Security_Team.xml
+++ b/public_html/lt-LT/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/lt-LT/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds.xml b/public_html/lt-LT/opds.xml
index 9ba66f6..ffeb075 100644
--- a/public_html/lt-LT/opds.xml
+++ b/public_html/lt-LT/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/lt-LT/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/lt-LT/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/lt-LT/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/lt-LT/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/lt-LT/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/lt-LT/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/lt-LT/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/lt-LT/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/lt-LT/toc.html b/public_html/lt-LT/toc.html
index 583a006..31ab9ac 100644
--- a/public_html/lt-LT/toc.html
+++ b/public_html/lt-LT/toc.html
@@ -124,6 +124,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Security-Enhanced_Linux' class="book collapsed" onclick="toggle(event, 'Fedora.21.Security-Enhanced_Linux.types');">
<a class="type" href="../en-US/Fedora/21/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Security-Enhanced_Linux/index.html'"><span class="book">Security-Enhanced Linux</span></a>
<div id='Fedora.21.Security-Enhanced_Linux.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/ml-IN/Site_Statistics.html b/public_html/ml-IN/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/ml-IN/Site_Statistics.html
+++ b/public_html/ml-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/ml-IN/opds-Community_Services_Infrastructure.xml b/public_html/ml-IN/opds-Community_Services_Infrastructure.xml
index ebf6096..89ad4a1 100644
--- a/public_html/ml-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ml-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora.xml b/public_html/ml-IN/opds-Fedora.xml
index ab16d5f..82591d2 100644
--- a/public_html/ml-IN/opds-Fedora.xml
+++ b/public_html/ml-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>ml-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
index 17c0087..a74df32 100644
--- a/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Core.xml b/public_html/ml-IN/opds-Fedora_Core.xml
index 82c4903..17d92d4 100644
--- a/public_html/ml-IN/opds-Fedora_Core.xml
+++ b/public_html/ml-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Documentation.xml b/public_html/ml-IN/opds-Fedora_Documentation.xml
index 2470e8d..b9bc5ca 100644
--- a/public_html/ml-IN/opds-Fedora_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml b/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
index 0b05918..6a1396f 100644
--- a/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Security_Team.xml b/public_html/ml-IN/opds-Fedora_Security_Team.xml
index 483812c..d615725 100644
--- a/public_html/ml-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/ml-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds.xml b/public_html/ml-IN/opds.xml
index 095fe29..5bacbf9 100644
--- a/public_html/ml-IN/opds.xml
+++ b/public_html/ml-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ml-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ml-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ml-IN/toc.html b/public_html/ml-IN/toc.html
index 18d4611..2a73fd9 100644
--- a/public_html/ml-IN/toc.html
+++ b/public_html/ml-IN/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/mr-IN/Site_Statistics.html b/public_html/mr-IN/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/mr-IN/Site_Statistics.html
+++ b/public_html/mr-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/mr-IN/opds-Community_Services_Infrastructure.xml b/public_html/mr-IN/opds-Community_Services_Infrastructure.xml
index bc95fed..910d287 100644
--- a/public_html/mr-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/mr-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora.xml b/public_html/mr-IN/opds-Fedora.xml
index 12ed55f..e923964 100644
--- a/public_html/mr-IN/opds-Fedora.xml
+++ b/public_html/mr-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>mr-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
index 342b77c..a6327a1 100644
--- a/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Core.xml b/public_html/mr-IN/opds-Fedora_Core.xml
index b5cc3ca..1e5b625 100644
--- a/public_html/mr-IN/opds-Fedora_Core.xml
+++ b/public_html/mr-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Documentation.xml b/public_html/mr-IN/opds-Fedora_Documentation.xml
index 9049592..a549b8f 100644
--- a/public_html/mr-IN/opds-Fedora_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml b/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
index 96bbcf2..3372036 100644
--- a/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Security_Team.xml b/public_html/mr-IN/opds-Fedora_Security_Team.xml
index c6142a8..8a0062e 100644
--- a/public_html/mr-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/mr-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds.xml b/public_html/mr-IN/opds.xml
index 521b32e..611dc32 100644
--- a/public_html/mr-IN/opds.xml
+++ b/public_html/mr-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/mr-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/mr-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/mr-IN/toc.html b/public_html/mr-IN/toc.html
index b88a3c7..cc02692 100644
--- a/public_html/mr-IN/toc.html
+++ b/public_html/mr-IN/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/nb-NO/Site_Statistics.html b/public_html/nb-NO/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/nb-NO/Site_Statistics.html
+++ b/public_html/nb-NO/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/nb-NO/opds-Community_Services_Infrastructure.xml b/public_html/nb-NO/opds-Community_Services_Infrastructure.xml
index a633861..de8bb3c 100644
--- a/public_html/nb-NO/opds-Community_Services_Infrastructure.xml
+++ b/public_html/nb-NO/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora.xml b/public_html/nb-NO/opds-Fedora.xml
index 2da0a4a..49dea74 100644
--- a/public_html/nb-NO/opds-Fedora.xml
+++ b/public_html/nb-NO/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>nb-NO</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml b/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
index da088bf..a65e6cf 100644
--- a/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Core.xml b/public_html/nb-NO/opds-Fedora_Core.xml
index 50abdc4..5c165c6 100644
--- a/public_html/nb-NO/opds-Fedora_Core.xml
+++ b/public_html/nb-NO/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Documentation.xml b/public_html/nb-NO/opds-Fedora_Documentation.xml
index 24c6a53..e7791a6 100644
--- a/public_html/nb-NO/opds-Fedora_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml b/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
index a884607..b1acc6c 100644
--- a/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Security_Team.xml b/public_html/nb-NO/opds-Fedora_Security_Team.xml
index 13986e1..274d1bd 100644
--- a/public_html/nb-NO/opds-Fedora_Security_Team.xml
+++ b/public_html/nb-NO/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds.xml b/public_html/nb-NO/opds.xml
index ea9018bd..1ace706 100644
--- a/public_html/nb-NO/opds.xml
+++ b/public_html/nb-NO/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/nb-NO/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/nb-NO/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/nb-NO/toc.html b/public_html/nb-NO/toc.html
index 85d4f21..e3d5fc4 100644
--- a/public_html/nb-NO/toc.html
+++ b/public_html/nb-NO/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/nl-NL/Site_Statistics.html b/public_html/nl-NL/Site_Statistics.html
index 0d7f349..2571c97 100644
--- a/public_html/nl-NL/Site_Statistics.html
+++ b/public_html/nl-NL/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Totaal talen: </b>45<br />
- <b>Totaal pakketten: </b>917
+ <b>Totaal pakketten: </b>918
</div>
</body>
</html>
diff --git a/public_html/nl-NL/opds-Community_Services_Infrastructure.xml b/public_html/nl-NL/opds-Community_Services_Infrastructure.xml
index 6f85316..b8b2fcb 100644
--- a/public_html/nl-NL/opds-Community_Services_Infrastructure.xml
+++ b/public_html/nl-NL/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora.xml b/public_html/nl-NL/opds-Fedora.xml
index 92e3db9..deaf99b 100644
--- a/public_html/nl-NL/opds-Fedora.xml
+++ b/public_html/nl-NL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>nl-NL</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Vrijgave-informatie</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-nl-NL.epub</id>
<!--author>
diff --git a/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml b/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
index a2eee5d..7952b06 100644
--- a/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Core.xml b/public_html/nl-NL/opds-Fedora_Core.xml
index d99105f..8122f44 100644
--- a/public_html/nl-NL/opds-Fedora_Core.xml
+++ b/public_html/nl-NL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Documentation.xml b/public_html/nl-NL/opds-Fedora_Documentation.xml
index 0f4b70d..88966a6 100644
--- a/public_html/nl-NL/opds-Fedora_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml b/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
index 4b8cf8f..7836dd6 100644
--- a/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Security_Team.xml b/public_html/nl-NL/opds-Fedora_Security_Team.xml
index 483233f..dc33d33 100644
--- a/public_html/nl-NL/opds-Fedora_Security_Team.xml
+++ b/public_html/nl-NL/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds.xml b/public_html/nl-NL/opds.xml
index 898287b..3c97ad0 100644
--- a/public_html/nl-NL/opds.xml
+++ b/public_html/nl-NL/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/nl-NL/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/nl-NL/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/nl-NL/toc.html b/public_html/nl-NL/toc.html
index 28ddec3..18f3485 100644
--- a/public_html/nl-NL/toc.html
+++ b/public_html/nl-NL/toc.html
@@ -124,6 +124,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Security-Enhanced_Linux' class="book collapsed" onclick="toggle(event, 'Fedora.21.Security-Enhanced_Linux.types');">
<a class="type" href="../en-US/Fedora/21/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Security-Enhanced_Linux/index.html'"><span class="book">Security-Enhanced Linux</span></a>
<div id='Fedora.21.Security-Enhanced_Linux.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/opds.xml b/public_html/opds.xml
index 44e402f..b33e457 100644
--- a/public_html/opds.xml
+++ b/public_html/opds.xml
@@ -7,7 +7,7 @@
<link rel="start" href="http://docs.fedoraproject.org/opds.xml" type="application/atom+xml;type=feed;profile=opds-catalog"/>
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<title>Fedora Documentation</title>
- <updated>2015-01-08T13:59:29</updated>
+ <updated>2015-01-08T14:06:29</updated>
<!--author>
<name></name>
<uri></uri>
@@ -16,7 +16,7 @@
<entry>
<title>অসমীয়া</title>
<id>as-IN/opds.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="as-IN/opds.xml"/>
@@ -24,7 +24,7 @@
<entry>
<title>български</title>
<id>bg-BG/opds.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bg-BG/opds.xml"/>
@@ -32,7 +32,7 @@
<entry>
<title>বাংলা</title>
<id>bn-IN/opds.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bn-IN/opds.xml"/>
@@ -40,7 +40,7 @@
<entry>
<title>Bosanski</title>
<id>bs-BA/opds.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bs-BA/opds.xml"/>
@@ -48,7 +48,7 @@
<entry>
<title>Català</title>
<id>ca-ES/opds.xml</id>
- <updated>2015-01-08T13:59:15</updated>
+ <updated>2015-01-08T14:06:21</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ca-ES/opds.xml"/>
@@ -56,7 +56,7 @@
<entry>
<title>Čeština</title>
<id>cs-CZ/opds.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="cs-CZ/opds.xml"/>
@@ -64,7 +64,7 @@
<entry>
<title>Dansk</title>
<id>da-DK/opds.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="da-DK/opds.xml"/>
@@ -72,7 +72,7 @@
<entry>
<title>Deutsch</title>
<id>de-DE/opds.xml</id>
- <updated>2015-01-08T13:59:16</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="de-DE/opds.xml"/>
@@ -80,7 +80,7 @@
<entry>
<title>Ελληνικά</title>
<id>el-GR/opds.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="el-GR/opds.xml"/>
@@ -88,7 +88,7 @@
<entry>
<title>English</title>
<id>en-US/opds.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="en-US/opds.xml"/>
@@ -96,7 +96,7 @@
<entry>
<title>Español</title>
<id>es-ES/opds.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:22</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="es-ES/opds.xml"/>
@@ -104,7 +104,7 @@
<entry>
<title>فارسی</title>
<id>fa-IR/opds.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fa-IR/opds.xml"/>
@@ -112,7 +112,7 @@
<entry>
<title>Suomi</title>
<id>fi-FI/opds.xml</id>
- <updated>2015-01-08T13:59:17</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fi-FI/opds.xml"/>
@@ -120,7 +120,7 @@
<entry>
<title>Français</title>
<id>fr-FR/opds.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fr-FR/opds.xml"/>
@@ -128,7 +128,7 @@
<entry>
<title>ગુજરાતી</title>
<id>gu-IN/opds.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="gu-IN/opds.xml"/>
@@ -136,7 +136,7 @@
<entry>
<title>עברית</title>
<id>he-IL/opds.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="he-IL/opds.xml"/>
@@ -144,7 +144,7 @@
<entry>
<title>हिन्दी</title>
<id>hi-IN/opds.xml</id>
- <updated>2015-01-08T13:59:18</updated>
+ <updated>2015-01-08T14:06:23</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="hi-IN/opds.xml"/>
@@ -152,7 +152,7 @@
<entry>
<title>Magyar</title>
<id>hu-HU/opds.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="hu-HU/opds.xml"/>
@@ -160,7 +160,7 @@
<entry>
<title>Interlingua (International Auxiliary Language Association)</title>
<id>ia/opds.xml</id>
- <updated>2015-01-08T13:59:19</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ia/opds.xml"/>
@@ -168,7 +168,7 @@
<entry>
<title>Indonesia</title>
<id>id-ID/opds.xml</id>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="id-ID/opds.xml"/>
@@ -176,7 +176,7 @@
<entry>
<title>Italiano</title>
<id>it-IT/opds.xml</id>
- <updated>2015-01-08T13:59:20</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="it-IT/opds.xml"/>
@@ -184,7 +184,7 @@
<entry>
<title>日本語</title>
<id>ja-JP/opds.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:24</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ja-JP/opds.xml"/>
@@ -192,7 +192,7 @@
<entry>
<title>ಕನ್ನಡ</title>
<id>kn-IN/opds.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="kn-IN/opds.xml"/>
@@ -200,7 +200,7 @@
<entry>
<title>한국어</title>
<id>ko-KR/opds.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ko-KR/opds.xml"/>
@@ -208,7 +208,7 @@
<entry>
<title>Lithuanian</title>
<id>lt-LT/opds.xml</id>
- <updated>2015-01-08T13:59:21</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="lt-LT/opds.xml"/>
@@ -216,7 +216,7 @@
<entry>
<title>മലയാളം</title>
<id>ml-IN/opds.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ml-IN/opds.xml"/>
@@ -224,7 +224,7 @@
<entry>
<title>मराठी</title>
<id>mr-IN/opds.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="mr-IN/opds.xml"/>
@@ -232,7 +232,7 @@
<entry>
<title>Norsk (bokmål)</title>
<id>nb-NO/opds.xml</id>
- <updated>2015-01-08T13:59:22</updated>
+ <updated>2015-01-08T14:06:25</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nb-NO/opds.xml"/>
@@ -240,7 +240,7 @@
<entry>
<title>Nederlands</title>
<id>nl-NL/opds.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nl-NL/opds.xml"/>
@@ -248,7 +248,7 @@
<entry>
<title>ଓଡ଼ିଆ</title>
<id>or-IN/opds.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="or-IN/opds.xml"/>
@@ -256,7 +256,7 @@
<entry>
<title>ਪੰਜਾਬੀ</title>
<id>pa-IN/opds.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pa-IN/opds.xml"/>
@@ -264,7 +264,7 @@
<entry>
<title>Polski</title>
<id>pl-PL/opds.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pl-PL/opds.xml"/>
@@ -272,7 +272,7 @@
<entry>
<title>Português Brasileiro</title>
<id>pt-BR/opds.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-BR/opds.xml"/>
@@ -280,7 +280,7 @@
<entry>
<title>Português</title>
<id>pt-PT/opds.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-PT/opds.xml"/>
@@ -288,7 +288,7 @@
<entry>
<title>Romanian</title>
<id>ro/opds.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ro/opds.xml"/>
@@ -296,7 +296,7 @@
<entry>
<title>Русский</title>
<id>ru-RU/opds.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ru-RU/opds.xml"/>
@@ -304,7 +304,7 @@
<entry>
<title>Slovenščina</title>
<id>sk-SK/opds.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sk-SK/opds.xml"/>
@@ -312,7 +312,7 @@
<entry>
<title>Srpski (latinica)</title>
<id>sr-Latn-RS/opds.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sr-Latn-RS/opds.xml"/>
@@ -320,7 +320,7 @@
<entry>
<title>Српски</title>
<id>sr-RS/opds.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sr-RS/opds.xml"/>
@@ -328,7 +328,7 @@
<entry>
<title>Svenska</title>
<id>sv-SE/opds.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sv-SE/opds.xml"/>
@@ -336,7 +336,7 @@
<entry>
<title>தமிழ்</title>
<id>ta-IN/opds.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ta-IN/opds.xml"/>
@@ -344,7 +344,7 @@
<entry>
<title>తెలుగు</title>
<id>te-IN/opds.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="te-IN/opds.xml"/>
@@ -352,7 +352,7 @@
<entry>
<title>Українська</title>
<id>uk-UA/opds.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="uk-UA/opds.xml"/>
@@ -360,7 +360,7 @@
<entry>
<title>简体中文</title>
<id>zh-CN/opds.xml</id>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="zh-CN/opds.xml"/>
@@ -368,7 +368,7 @@
<entry>
<title>繁體中文</title>
<id>zh-TW/opds.xml</id>
- <updated>2015-01-08T13:59:29</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="zh-TW/opds.xml"/>
diff --git a/public_html/or-IN/Site_Statistics.html b/public_html/or-IN/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/or-IN/Site_Statistics.html
+++ b/public_html/or-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/or-IN/opds-Community_Services_Infrastructure.xml b/public_html/or-IN/opds-Community_Services_Infrastructure.xml
index f58d417..bdfe660 100644
--- a/public_html/or-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/or-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora.xml b/public_html/or-IN/opds-Fedora.xml
index c265041..236f1cc 100644
--- a/public_html/or-IN/opds-Fedora.xml
+++ b/public_html/or-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>or-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
index 2db7c7e..471d272 100644
--- a/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Core.xml b/public_html/or-IN/opds-Fedora_Core.xml
index c040bd4..20167c8 100644
--- a/public_html/or-IN/opds-Fedora_Core.xml
+++ b/public_html/or-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Documentation.xml b/public_html/or-IN/opds-Fedora_Documentation.xml
index 4272423..617c91b 100644
--- a/public_html/or-IN/opds-Fedora_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Draft_Documentation.xml b/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
index ea51e8b..6a1449d 100644
--- a/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Security_Team.xml b/public_html/or-IN/opds-Fedora_Security_Team.xml
index b87ecaf..641a943 100644
--- a/public_html/or-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/or-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds.xml b/public_html/or-IN/opds.xml
index 03ed693..58b50d8 100644
--- a/public_html/or-IN/opds.xml
+++ b/public_html/or-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/or-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/or-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/or-IN/toc.html b/public_html/or-IN/toc.html
index edd6d3d..edeec70 100644
--- a/public_html/or-IN/toc.html
+++ b/public_html/or-IN/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/pa-IN/Site_Statistics.html b/public_html/pa-IN/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/pa-IN/Site_Statistics.html
+++ b/public_html/pa-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/pa-IN/opds-Community_Services_Infrastructure.xml b/public_html/pa-IN/opds-Community_Services_Infrastructure.xml
index b30f1b0..44e34f3 100644
--- a/public_html/pa-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pa-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora.xml b/public_html/pa-IN/opds-Fedora.xml
index 25f9a23..9e8e0e2 100644
--- a/public_html/pa-IN/opds-Fedora.xml
+++ b/public_html/pa-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>pa-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
index d469820..884900d 100644
--- a/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Core.xml b/public_html/pa-IN/opds-Fedora_Core.xml
index 49e614a..30ecd85 100644
--- a/public_html/pa-IN/opds-Fedora_Core.xml
+++ b/public_html/pa-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Documentation.xml b/public_html/pa-IN/opds-Fedora_Documentation.xml
index 1e27244..b965bd9 100644
--- a/public_html/pa-IN/opds-Fedora_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml b/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
index 4276fc7..ff983b5 100644
--- a/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Security_Team.xml b/public_html/pa-IN/opds-Fedora_Security_Team.xml
index 3b94cea..f6d4fa1 100644
--- a/public_html/pa-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/pa-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds.xml b/public_html/pa-IN/opds.xml
index 4c6cd55..197bfb2 100644
--- a/public_html/pa-IN/opds.xml
+++ b/public_html/pa-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pa-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/pa-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pa-IN/toc.html b/public_html/pa-IN/toc.html
index a216d1c..7eb3814 100644
--- a/public_html/pa-IN/toc.html
+++ b/public_html/pa-IN/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/pl-PL/Site_Statistics.html b/public_html/pl-PL/Site_Statistics.html
index 69e5803..e18ed60 100644
--- a/public_html/pl-PL/Site_Statistics.html
+++ b/public_html/pl-PL/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Razem języków: </b>45<br />
- <b>Razem pakietów: </b>917
+ <b>Razem pakietów: </b>918
</div>
</body>
</html>
diff --git a/public_html/pl-PL/opds-Community_Services_Infrastructure.xml b/public_html/pl-PL/opds-Community_Services_Infrastructure.xml
index b4e7622..d18d9b9 100644
--- a/public_html/pl-PL/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pl-PL/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora.xml b/public_html/pl-PL/opds-Fedora.xml
index 66af680..c46039a 100644
--- a/public_html/pl-PL/opds-Fedora.xml
+++ b/public_html/pl-PL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>pl-PL</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml b/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
index 3455c7d..f267278 100644
--- a/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Contributor_Documentation.xml</id>
<title>Dokumentacja dla współtwórców Fedory</title>
<subtitle>Dokumentacja dla współtwórców Fedory</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Core.xml b/public_html/pl-PL/opds-Fedora_Core.xml
index 862f3cf..2a56cbe 100644
--- a/public_html/pl-PL/opds-Fedora_Core.xml
+++ b/public_html/pl-PL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Documentation.xml b/public_html/pl-PL/opds-Fedora_Documentation.xml
index 6d91751..ad1ddc4 100644
--- a/public_html/pl-PL/opds-Fedora_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml b/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
index 0f3a7e1..9578198 100644
--- a/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Security_Team.xml b/public_html/pl-PL/opds-Fedora_Security_Team.xml
index 635c199..ec7b038 100644
--- a/public_html/pl-PL/opds-Fedora_Security_Team.xml
+++ b/public_html/pl-PL/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds.xml b/public_html/pl-PL/opds.xml
index b548116..b07e51b 100644
--- a/public_html/pl-PL/opds.xml
+++ b/public_html/pl-PL/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pl-PL/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/pl-PL/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Dokumentacja dla współtwórców Fedory</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pl-PL/toc.html b/public_html/pl-PL/toc.html
index 9eeef9b..03e6d1c 100644
--- a/public_html/pl-PL/toc.html
+++ b/public_html/pl-PL/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/pt-BR/Site_Statistics.html b/public_html/pt-BR/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/pt-BR/Site_Statistics.html
+++ b/public_html/pt-BR/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/pt-BR/opds-Community_Services_Infrastructure.xml b/public_html/pt-BR/opds-Community_Services_Infrastructure.xml
index ae457f0..01b8ad9 100644
--- a/public_html/pt-BR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pt-BR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora.xml b/public_html/pt-BR/opds-Fedora.xml
index 97ed622..57cc160 100644
--- a/public_html/pt-BR/opds-Fedora.xml
+++ b/public_html/pt-BR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>pt-BR</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml b/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
index 318da48..898029b 100644
--- a/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Core.xml b/public_html/pt-BR/opds-Fedora_Core.xml
index b3b625f..fac2a02 100644
--- a/public_html/pt-BR/opds-Fedora_Core.xml
+++ b/public_html/pt-BR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Documentation.xml b/public_html/pt-BR/opds-Fedora_Documentation.xml
index 78651e0..df79737 100644
--- a/public_html/pt-BR/opds-Fedora_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml b/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
index d7d7bda..182fb68 100644
--- a/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Security_Team.xml b/public_html/pt-BR/opds-Fedora_Security_Team.xml
index 4c85e27..77178bf 100644
--- a/public_html/pt-BR/opds-Fedora_Security_Team.xml
+++ b/public_html/pt-BR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds.xml b/public_html/pt-BR/opds.xml
index 1fde032..f4b83a2 100644
--- a/public_html/pt-BR/opds.xml
+++ b/public_html/pt-BR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pt-BR/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/pt-BR/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:23</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pt-BR/toc.html b/public_html/pt-BR/toc.html
index b430dc4..8994414 100644
--- a/public_html/pt-BR/toc.html
+++ b/public_html/pt-BR/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/pt-PT/Site_Statistics.html b/public_html/pt-PT/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/pt-PT/Site_Statistics.html
+++ b/public_html/pt-PT/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/pt-PT/opds-Community_Services_Infrastructure.xml b/public_html/pt-PT/opds-Community_Services_Infrastructure.xml
index 5703482..dbd3c54 100644
--- a/public_html/pt-PT/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pt-PT/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora.xml b/public_html/pt-PT/opds-Fedora.xml
index d5a2c89..da55f31 100644
--- a/public_html/pt-PT/opds-Fedora.xml
+++ b/public_html/pt-PT/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>pt-PT</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml b/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
index f35c625..6814137 100644
--- a/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Core.xml b/public_html/pt-PT/opds-Fedora_Core.xml
index 3a13db1..aba6cdd 100644
--- a/public_html/pt-PT/opds-Fedora_Core.xml
+++ b/public_html/pt-PT/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Documentation.xml b/public_html/pt-PT/opds-Fedora_Documentation.xml
index 7763622..f2dd7eb 100644
--- a/public_html/pt-PT/opds-Fedora_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml b/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
index bd9d973..efc727a 100644
--- a/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Security_Team.xml b/public_html/pt-PT/opds-Fedora_Security_Team.xml
index 0d1d850..d66cfee 100644
--- a/public_html/pt-PT/opds-Fedora_Security_Team.xml
+++ b/public_html/pt-PT/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds.xml b/public_html/pt-PT/opds.xml
index 02d91cf..9f73a96 100644
--- a/public_html/pt-PT/opds.xml
+++ b/public_html/pt-PT/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pt-PT/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/pt-PT/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pt-PT/toc.html b/public_html/pt-PT/toc.html
index 9ccb181..a0b9a4a 100644
--- a/public_html/pt-PT/toc.html
+++ b/public_html/pt-PT/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/ro/Site_Statistics.html b/public_html/ro/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/ro/Site_Statistics.html
+++ b/public_html/ro/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/ro/opds-Community_Services_Infrastructure.xml b/public_html/ro/opds-Community_Services_Infrastructure.xml
index 8195ff3..0e9eb1c 100644
--- a/public_html/ro/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ro/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora.xml b/public_html/ro/opds-Fedora.xml
index 9709566..46cf32f 100644
--- a/public_html/ro/opds-Fedora.xml
+++ b/public_html/ro/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/ro/opds-Fedora_Contributor_Documentation.xml b/public_html/ro/opds-Fedora_Contributor_Documentation.xml
index ac544f8..a3d0fe7 100644
--- a/public_html/ro/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ro/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora_Core.xml b/public_html/ro/opds-Fedora_Core.xml
index d784ce4..91338e1 100644
--- a/public_html/ro/opds-Fedora_Core.xml
+++ b/public_html/ro/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora_Documentation.xml b/public_html/ro/opds-Fedora_Documentation.xml
index 60a508c..a183e99 100644
--- a/public_html/ro/opds-Fedora_Documentation.xml
+++ b/public_html/ro/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora_Draft_Documentation.xml b/public_html/ro/opds-Fedora_Draft_Documentation.xml
index 5fd5465..867f190 100644
--- a/public_html/ro/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ro/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora_Draft_Documentation.xml</id>
<title>Schiță Documentație Fedora</title>
<subtitle>Schiță Documentație Fedora</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora_Security_Team.xml b/public_html/ro/opds-Fedora_Security_Team.xml
index a779611..ae9fee9 100644
--- a/public_html/ro/opds-Fedora_Security_Team.xml
+++ b/public_html/ro/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds.xml b/public_html/ro/opds.xml
index 76fd5ef..7a840f9 100644
--- a/public_html/ro/opds.xml
+++ b/public_html/ro/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ro/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ro/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:26</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ro/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ro/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ro/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ro/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Schiță Documentație Fedora</title>
<id>http://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ro/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:24</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ro/toc.html b/public_html/ro/toc.html
index c2540a6..e6b438b 100644
--- a/public_html/ro/toc.html
+++ b/public_html/ro/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/ru-RU/Site_Statistics.html b/public_html/ru-RU/Site_Statistics.html
index e671642..c9de4aa 100644
--- a/public_html/ru-RU/Site_Statistics.html
+++ b/public_html/ru-RU/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Всего языков: </b>45<br />
- <b>Всего пакетов: </b>917
+ <b>Всего пакетов: </b>918
</div>
</body>
</html>
diff --git a/public_html/ru-RU/opds-Community_Services_Infrastructure.xml b/public_html/ru-RU/opds-Community_Services_Infrastructure.xml
index 0281b66..46deb52 100644
--- a/public_html/ru-RU/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ru-RU/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora.xml b/public_html/ru-RU/opds-Fedora.xml
index 49c55e5..ebe491e 100644
--- a/public_html/ru-RU/opds-Fedora.xml
+++ b/public_html/ru-RU/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>ru-RU</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml b/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
index 2919ed3..cc6bbac 100644
--- a/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Contributor_Documentation.xml</id>
<title>Документация участника Fedora</title>
<subtitle>Документация участника Fedora</subtitle>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Core.xml b/public_html/ru-RU/opds-Fedora_Core.xml
index 56ba0c6..91cf74a 100644
--- a/public_html/ru-RU/opds-Fedora_Core.xml
+++ b/public_html/ru-RU/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Documentation.xml b/public_html/ru-RU/opds-Fedora_Documentation.xml
index 520a775..8109554 100644
--- a/public_html/ru-RU/opds-Fedora_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml b/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
index 6ee4f06..b003bde 100644
--- a/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Security_Team.xml b/public_html/ru-RU/opds-Fedora_Security_Team.xml
index a1b5015..639f07d 100644
--- a/public_html/ru-RU/opds-Fedora_Security_Team.xml
+++ b/public_html/ru-RU/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds.xml b/public_html/ru-RU/opds.xml
index bb95d5e..94bb817 100644
--- a/public_html/ru-RU/opds.xml
+++ b/public_html/ru-RU/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ru-RU/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ru-RU/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Документация участника Fedora</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ru-RU/toc.html b/public_html/ru-RU/toc.html
index fea744f..f1f85d8 100644
--- a/public_html/ru-RU/toc.html
+++ b/public_html/ru-RU/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/sk-SK/Site_Statistics.html b/public_html/sk-SK/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/sk-SK/Site_Statistics.html
+++ b/public_html/sk-SK/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/sk-SK/opds-Community_Services_Infrastructure.xml b/public_html/sk-SK/opds-Community_Services_Infrastructure.xml
index ca05d19..45398b7 100644
--- a/public_html/sk-SK/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sk-SK/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora.xml b/public_html/sk-SK/opds-Fedora.xml
index c9d321f..bb7ae94 100644
--- a/public_html/sk-SK/opds-Fedora.xml
+++ b/public_html/sk-SK/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>sk-SK</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml b/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
index 377b9cd..147c2eb 100644
--- a/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Core.xml b/public_html/sk-SK/opds-Fedora_Core.xml
index a3c1eaf..8ec1a8f 100644
--- a/public_html/sk-SK/opds-Fedora_Core.xml
+++ b/public_html/sk-SK/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Documentation.xml b/public_html/sk-SK/opds-Fedora_Documentation.xml
index fb658c6..265eb52 100644
--- a/public_html/sk-SK/opds-Fedora_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml b/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
index 779f40c..f15357e 100644
--- a/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Security_Team.xml b/public_html/sk-SK/opds-Fedora_Security_Team.xml
index e55c5a6..9edc040 100644
--- a/public_html/sk-SK/opds-Fedora_Security_Team.xml
+++ b/public_html/sk-SK/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds.xml b/public_html/sk-SK/opds.xml
index c333b59..d675514 100644
--- a/public_html/sk-SK/opds.xml
+++ b/public_html/sk-SK/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sk-SK/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/sk-SK/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sk-SK/toc.html b/public_html/sk-SK/toc.html
index d1b6935..eae940f 100644
--- a/public_html/sk-SK/toc.html
+++ b/public_html/sk-SK/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/sr-Latn-RS/Site_Statistics.html b/public_html/sr-Latn-RS/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/sr-Latn-RS/Site_Statistics.html
+++ b/public_html/sr-Latn-RS/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml b/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml
index 2ceb36d..090177c 100644
--- a/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora.xml b/public_html/sr-Latn-RS/opds-Fedora.xml
index 70d3a63..fbca9ae 100644
--- a/public_html/sr-Latn-RS/opds-Fedora.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>sr-Latn-RS</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml b/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
index 6f02edd..f8a8f33 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Core.xml b/public_html/sr-Latn-RS/opds-Fedora_Core.xml
index c542a0f..7280c99 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Core.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Documentation.xml b/public_html/sr-Latn-RS/opds-Fedora_Documentation.xml
index 60712c3..debc8c9 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml b/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
index ab5086f..8bfad8e 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml b/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml
index 160a97e..9f1885a 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds.xml b/public_html/sr-Latn-RS/opds.xml
index 406571a..d5604e4 100644
--- a/public_html/sr-Latn-RS/opds.xml
+++ b/public_html/sr-Latn-RS/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:25</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sr-Latn-RS/toc.html b/public_html/sr-Latn-RS/toc.html
index 30bac46..7486521 100644
--- a/public_html/sr-Latn-RS/toc.html
+++ b/public_html/sr-Latn-RS/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/sr-RS/Site_Statistics.html b/public_html/sr-RS/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/sr-RS/Site_Statistics.html
+++ b/public_html/sr-RS/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/sr-RS/opds-Community_Services_Infrastructure.xml b/public_html/sr-RS/opds-Community_Services_Infrastructure.xml
index 60ede96..af88d43 100644
--- a/public_html/sr-RS/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sr-RS/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora.xml b/public_html/sr-RS/opds-Fedora.xml
index abc2372..9697229 100644
--- a/public_html/sr-RS/opds-Fedora.xml
+++ b/public_html/sr-RS/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>sr-RS</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml b/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
index 5828f35..27573a9 100644
--- a/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Core.xml b/public_html/sr-RS/opds-Fedora_Core.xml
index 3745419..4c261d9 100644
--- a/public_html/sr-RS/opds-Fedora_Core.xml
+++ b/public_html/sr-RS/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Documentation.xml b/public_html/sr-RS/opds-Fedora_Documentation.xml
index 441516e..e91fb57 100644
--- a/public_html/sr-RS/opds-Fedora_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml b/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
index 5f14edb..d0525eb 100644
--- a/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Security_Team.xml b/public_html/sr-RS/opds-Fedora_Security_Team.xml
index 46e3664..e439ec0 100644
--- a/public_html/sr-RS/opds-Fedora_Security_Team.xml
+++ b/public_html/sr-RS/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds.xml b/public_html/sr-RS/opds.xml
index 2f3da7f..d25d8df 100644
--- a/public_html/sr-RS/opds.xml
+++ b/public_html/sr-RS/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sr-RS/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/sr-RS/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sr-RS/toc.html b/public_html/sr-RS/toc.html
index d86f5a4..240b33e 100644
--- a/public_html/sr-RS/toc.html
+++ b/public_html/sr-RS/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/sv-SE/Site_Statistics.html b/public_html/sv-SE/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/sv-SE/Site_Statistics.html
+++ b/public_html/sv-SE/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/sv-SE/opds-Community_Services_Infrastructure.xml b/public_html/sv-SE/opds-Community_Services_Infrastructure.xml
index 2710558..ef545ff 100644
--- a/public_html/sv-SE/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sv-SE/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora.xml b/public_html/sv-SE/opds-Fedora.xml
index aa197ec..8e79b66 100644
--- a/public_html/sv-SE/opds-Fedora.xml
+++ b/public_html/sv-SE/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>sv-SE</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml b/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
index 19698a9..e9d5d15 100644
--- a/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Core.xml b/public_html/sv-SE/opds-Fedora_Core.xml
index 4516b19..08ed9e1 100644
--- a/public_html/sv-SE/opds-Fedora_Core.xml
+++ b/public_html/sv-SE/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Documentation.xml b/public_html/sv-SE/opds-Fedora_Documentation.xml
index 0619799..b4f71c0 100644
--- a/public_html/sv-SE/opds-Fedora_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml b/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
index 220be42..b7b0a67 100644
--- a/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Security_Team.xml b/public_html/sv-SE/opds-Fedora_Security_Team.xml
index f113cf2..ac16ca4 100644
--- a/public_html/sv-SE/opds-Fedora_Security_Team.xml
+++ b/public_html/sv-SE/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds.xml b/public_html/sv-SE/opds.xml
index f70fbf6..c5ef462 100644
--- a/public_html/sv-SE/opds.xml
+++ b/public_html/sv-SE/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sv-SE/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/sv-SE/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:27</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sv-SE/toc.html b/public_html/sv-SE/toc.html
index f9b4104..ea51c47 100644
--- a/public_html/sv-SE/toc.html
+++ b/public_html/sv-SE/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/ta-IN/Site_Statistics.html b/public_html/ta-IN/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/ta-IN/Site_Statistics.html
+++ b/public_html/ta-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/ta-IN/opds-Community_Services_Infrastructure.xml b/public_html/ta-IN/opds-Community_Services_Infrastructure.xml
index 185a0a4..ae8ef3a 100644
--- a/public_html/ta-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ta-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora.xml b/public_html/ta-IN/opds-Fedora.xml
index 9925cdb..4ddbbf7 100644
--- a/public_html/ta-IN/opds-Fedora.xml
+++ b/public_html/ta-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>ta-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
index b3126f5..157a09a 100644
--- a/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Core.xml b/public_html/ta-IN/opds-Fedora_Core.xml
index 54cb8a6..42b2708 100644
--- a/public_html/ta-IN/opds-Fedora_Core.xml
+++ b/public_html/ta-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Documentation.xml b/public_html/ta-IN/opds-Fedora_Documentation.xml
index 4862651..c9d9317 100644
--- a/public_html/ta-IN/opds-Fedora_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml b/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
index ddd78cf..aae0b28 100644
--- a/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Security_Team.xml b/public_html/ta-IN/opds-Fedora_Security_Team.xml
index 98377e3..2431fc0 100644
--- a/public_html/ta-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/ta-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds.xml b/public_html/ta-IN/opds.xml
index 86fd71c..def86ad 100644
--- a/public_html/ta-IN/opds.xml
+++ b/public_html/ta-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ta-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ta-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:26</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ta-IN/toc.html b/public_html/ta-IN/toc.html
index 9473cae..16ef28a 100644
--- a/public_html/ta-IN/toc.html
+++ b/public_html/ta-IN/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/te-IN/Site_Statistics.html b/public_html/te-IN/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/te-IN/Site_Statistics.html
+++ b/public_html/te-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/te-IN/opds-Community_Services_Infrastructure.xml b/public_html/te-IN/opds-Community_Services_Infrastructure.xml
index 886a30b..451a8ed 100644
--- a/public_html/te-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/te-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora.xml b/public_html/te-IN/opds-Fedora.xml
index ca97904..56173f3 100644
--- a/public_html/te-IN/opds-Fedora.xml
+++ b/public_html/te-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>te-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
index 7f85eeb..f13c792 100644
--- a/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Core.xml b/public_html/te-IN/opds-Fedora_Core.xml
index 2651735..570512c 100644
--- a/public_html/te-IN/opds-Fedora_Core.xml
+++ b/public_html/te-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Documentation.xml b/public_html/te-IN/opds-Fedora_Documentation.xml
index 5295a3b..a16347a 100644
--- a/public_html/te-IN/opds-Fedora_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Draft_Documentation.xml b/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
index 94eb682..452f57c 100644
--- a/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Security_Team.xml b/public_html/te-IN/opds-Fedora_Security_Team.xml
index adeac91..bded13c 100644
--- a/public_html/te-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/te-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds.xml b/public_html/te-IN/opds.xml
index 937567f..addee4e 100644
--- a/public_html/te-IN/opds.xml
+++ b/public_html/te-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/te-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/te-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/te-IN/toc.html b/public_html/te-IN/toc.html
index b719728..5948318 100644
--- a/public_html/te-IN/toc.html
+++ b/public_html/te-IN/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/toc.html b/public_html/toc.html
index ea57ba8..9eb025a 100644
--- a/public_html/toc.html
+++ b/public_html/toc.html
@@ -1620,6 +1620,21 @@
</div>
<div class="book">
+ <span id="Networking_Guide" class="book">Networking Guide</span>
+ <div class="types">
+
+ <a class="type" href="./en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">epub</a>
+
+ <a class="type" href="./en-US/Fedora/21/html/Networking_Guide/index.html">html</a>
+
+ <a class="type" href="./en-US/Fedora/21/html-single/Networking_Guide/index.html">html-single</a>
+
+ <a class="type" href="./en-US/Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf">pdf</a>
+
+ </div>
+ </div>
+
+ <div class="book">
<span id="Release_Notes" class="book">Release Notes</span>
<div class="types">
diff --git a/public_html/uk-UA/Site_Statistics.html b/public_html/uk-UA/Site_Statistics.html
index d652a65..63fb23d 100644
--- a/public_html/uk-UA/Site_Statistics.html
+++ b/public_html/uk-UA/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Загалом мов: </b>45<br />
- <b>Загалом пакунків: </b>917
+ <b>Загалом пакунків: </b>918
</div>
</body>
</html>
diff --git a/public_html/uk-UA/opds-Community_Services_Infrastructure.xml b/public_html/uk-UA/opds-Community_Services_Infrastructure.xml
index 79f485b..99de30a 100644
--- a/public_html/uk-UA/opds-Community_Services_Infrastructure.xml
+++ b/public_html/uk-UA/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora.xml b/public_html/uk-UA/opds-Fedora.xml
index 1a9739b..6405b8d 100644
--- a/public_html/uk-UA/opds-Fedora.xml
+++ b/public_html/uk-UA/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>uk-UA</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Нотатки щодо випуску</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-uk-UA.epub</id>
<!--author>
diff --git a/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml b/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
index 6f97961..7d13012 100644
--- a/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Contributor_Documentation.xml</id>
<title>Документація для учасника розробки Fedora</title>
<subtitle>Документація для учасника розробки Fedora</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Core.xml b/public_html/uk-UA/opds-Fedora_Core.xml
index 6ef57ab..393c7b8 100644
--- a/public_html/uk-UA/opds-Fedora_Core.xml
+++ b/public_html/uk-UA/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Documentation.xml b/public_html/uk-UA/opds-Fedora_Documentation.xml
index 8591747..581c2d3 100644
--- a/public_html/uk-UA/opds-Fedora_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml b/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
index ff903d6..30ea1c5 100644
--- a/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Draft_Documentation.xml</id>
<title>Чернетки документації з Fedora</title>
<subtitle>Чернетки документації з Fedora</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Security_Team.xml b/public_html/uk-UA/opds-Fedora_Security_Team.xml
index 4b52a10..1ac4407 100644
--- a/public_html/uk-UA/opds-Fedora_Security_Team.xml
+++ b/public_html/uk-UA/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds.xml b/public_html/uk-UA/opds.xml
index db644e3..6c156c6 100644
--- a/public_html/uk-UA/opds.xml
+++ b/public_html/uk-UA/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/uk-UA/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/uk-UA/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Документація для учасника розробки Fedora</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Чернетки документації з Fedora</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:27</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/uk-UA/toc.html b/public_html/uk-UA/toc.html
index 81237e8..1bdb7aa 100644
--- a/public_html/uk-UA/toc.html
+++ b/public_html/uk-UA/toc.html
@@ -124,6 +124,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Security-Enhanced_Linux' class="book collapsed" onclick="toggle(event, 'Fedora.21.Security-Enhanced_Linux.types');">
<a class="type" href="../en-US/Fedora/21/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Security-Enhanced_Linux/index.html'"><span class="book">Security-Enhanced Linux</span></a>
<div id='Fedora.21.Security-Enhanced_Linux.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/zh-CN/Site_Statistics.html b/public_html/zh-CN/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/zh-CN/Site_Statistics.html
+++ b/public_html/zh-CN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/zh-CN/opds-Community_Services_Infrastructure.xml b/public_html/zh-CN/opds-Community_Services_Infrastructure.xml
index 952438a..95e1c1b 100644
--- a/public_html/zh-CN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/zh-CN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora.xml b/public_html/zh-CN/opds-Fedora.xml
index 15d1710..c40578c 100644
--- a/public_html/zh-CN/opds-Fedora.xml
+++ b/public_html/zh-CN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>zh-CN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>发行注记</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-zh-CN.epub</id>
<!--author>
diff --git a/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml b/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
index c4f4095..e7e8fc8 100644
--- a/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Core.xml b/public_html/zh-CN/opds-Fedora_Core.xml
index 21cf9b2..baaa6a5 100644
--- a/public_html/zh-CN/opds-Fedora_Core.xml
+++ b/public_html/zh-CN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Documentation.xml b/public_html/zh-CN/opds-Fedora_Documentation.xml
index 268d780..3f86c38 100644
--- a/public_html/zh-CN/opds-Fedora_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml b/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
index 439c400..3b64039 100644
--- a/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Security_Team.xml b/public_html/zh-CN/opds-Fedora_Security_Team.xml
index f94e7bb..0559a3c 100644
--- a/public_html/zh-CN/opds-Fedora_Security_Team.xml
+++ b/public_html/zh-CN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds.xml b/public_html/zh-CN/opds.xml
index da2922e..aedd5d3 100644
--- a/public_html/zh-CN/opds.xml
+++ b/public_html/zh-CN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/zh-CN/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/zh-CN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/zh-CN/toc.html b/public_html/zh-CN/toc.html
index 9623929..f2bbdfc 100644
--- a/public_html/zh-CN/toc.html
+++ b/public_html/zh-CN/toc.html
@@ -124,6 +124,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Security-Enhanced_Linux' class="book collapsed" onclick="toggle(event, 'Fedora.21.Security-Enhanced_Linux.types');">
<a class="type" href="../en-US/Fedora/21/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Security-Enhanced_Linux/index.html'"><span class="book">Security-Enhanced Linux</span></a>
<div id='Fedora.21.Security-Enhanced_Linux.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/zh-TW/Site_Statistics.html b/public_html/zh-TW/Site_Statistics.html
index 1c520cc..1f6385f 100644
--- a/public_html/zh-TW/Site_Statistics.html
+++ b/public_html/zh-TW/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>7</td>
<td>45</td>
<td>23</td>
- <td>171</td>
+ <td>172</td>
</tr>
<tr>
@@ -430,7 +430,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>45<br />
- <b>Total Packages: </b>917
+ <b>Total Packages: </b>918
</div>
</body>
</html>
diff --git a/public_html/zh-TW/opds-Community_Services_Infrastructure.xml b/public_html/zh-TW/opds-Community_Services_Infrastructure.xml
index 1007f5d..49ce242 100644
--- a/public_html/zh-TW/opds-Community_Services_Infrastructure.xml
+++ b/public_html/zh-TW/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora.xml b/public_html/zh-TW/opds-Fedora.xml
index 39c3f3c..52d1ece 100644
--- a/public_html/zh-TW/opds-Fedora.xml
+++ b/public_html/zh-TW/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
@@ -31,6 +31,24 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Networking Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2015-01-08</updated>
+ <dc:language>zh-TW</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Configuration and Administration of networking for Fedora 20</summary>
+ <content type="text">The Networking Guide documents relevant information regarding the configuration and administration of network interfaces, networks and network services in Fedora 20. It is oriented towards system administrators with a basic understanding of Linux and networking. This book is based on the Deployment Guide from Red Hat Enterprise Linux 6. The chapters related to networking were taken from the Deployment Guide to form the foundation for this book.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Release Notes</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/21/epub/Release_Notes/Fedora-21-Release_Notes-en-US.epub</id>
<!--author>
diff --git a/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml b/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
index 190249c..387487a 100644
--- a/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Core.xml b/public_html/zh-TW/opds-Fedora_Core.xml
index 2381ebb..f9d1b91 100644
--- a/public_html/zh-TW/opds-Fedora_Core.xml
+++ b/public_html/zh-TW/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-01-08T13:59:29</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Documentation.xml b/public_html/zh-TW/opds-Fedora_Documentation.xml
index 3c0f908..d90c847 100644
--- a/public_html/zh-TW/opds-Fedora_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-01-08T13:59:29</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml b/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
index d62c055..3e5b692 100644
--- a/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-01-08T13:59:29</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Security_Team.xml b/public_html/zh-TW/opds-Fedora_Security_Team.xml
index d0a601f..09ca280 100644
--- a/public_html/zh-TW/opds-Fedora_Security_Team.xml
+++ b/public_html/zh-TW/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-01-08T13:59:29</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds.xml b/public_html/zh-TW/opds.xml
index 5dc1704..173ed64 100644
--- a/public_html/zh-TW/opds.xml
+++ b/public_html/zh-TW/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/zh-TW/opds.xml</id>
<title>Product List</title>
- <updated>2015-01-08T13:59:29</updated>
+ <updated>2015-01-08T14:06:28</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/zh-TW/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora/opds-Fedora.xml</id>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-01-08T13:59:28</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-01-08T13:59:29</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-01-08T13:59:29</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-01-08T13:59:29</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-01-08T13:59:29</updated>
+ <updated>2015-01-08T14:06:28</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/zh-TW/toc.html b/public_html/zh-TW/toc.html
index a000f74..d695e14 100644
--- a/public_html/zh-TW/toc.html
+++ b/public_html/zh-TW/toc.html
@@ -115,6 +115,15 @@
<a class="type" href="../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Installation_Guide/Fedora-21-Installation_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.21.Networking_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.21.Networking_Guide.types');">
+ <a class="type" href="../en-US/Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Networking_Guide/index.html'"><span class="book">Networking Guide</span></a>
+ <div id='Fedora.21.Networking_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/21/epub/Networking_Guide/Fedora-21-Networking_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/21/html/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html/Networking_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/21/html-single/Networking_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/21/html-single/Networking_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/21/pdf/Networking_Guide/Fedora-21-Networking_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.21.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.21.Release_Notes.types');">
<a class="type" href="../en-US/Fedora/21/html/Release_Notes/index.html" onclick="window.top.location='../en-US/Fedora/21/html/Release_Notes/index.html'"><span class="book">Release Notes</span></a>
<div id='Fedora.21.Release_Notes.types' class="types hidden" onclick="work=0;">
More information about the docs-commits
mailing list