Gentoo Archives: gentoo-doc-cvs

From: Josh Saddler <nightmorph@××××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: vpnc-howto.xml metadoc.xml
Date: Wed, 27 Jun 2007 20:19:17
Message-Id: E1I3dyb-0000JB-3e@stork.gentoo.org
1 nightmorph 07/06/27 20:18:57
2
3 Modified: vpnc-howto.xml metadoc.xml
4 Log:
5 vpnc final cleanups and moving to official 1.0 status, bug 97760 and bug 30966
6
7 Revision Changes Path
8 1.2 xml/htdocs/doc/en/vpnc-howto.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/vpnc-howto.xml?rev=1.2&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/vpnc-howto.xml?rev=1.2&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/vpnc-howto.xml?r1=1.1&r2=1.2
13
14 Index: vpnc-howto.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/vpnc-howto.xml,v
17 retrieving revision 1.1
18 retrieving revision 1.2
19 diff -u -r1.1 -r1.2
20 --- vpnc-howto.xml 23 May 2007 08:50:13 -0000 1.1
21 +++ vpnc-howto.xml 27 Jun 2007 20:18:57 -0000 1.2
22 @@ -1,8 +1,8 @@
23 <?xml version='1.0' encoding='UTF-8'?>
24 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vpnc-howto.xml,v 1.1 2007/05/23 08:50:13 neysx Exp $ -->
25 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vpnc-howto.xml,v 1.2 2007/06/27 20:18:57 nightmorph Exp $ -->
26 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
27
28 -<guide link="/doc/en/vpnc-howto.xml" disclaimer="draft">
29 +<guide link="/doc/en/vpnc-howto.xml">
30
31 <title>Gentoo vpnc HOWTO</title>
32
33 @@ -25,8 +25,8 @@
34 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
35 <license/>
36
37 -<version>0.14</version>
38 -<date>2007-05-23</date>
39 +<version>1.0</version>
40 +<date>2007-06-27</date>
41
42 <chapter>
43 <title>Introduction</title>
44 @@ -37,7 +37,7 @@
45 If you're reading this, then you likely need to connect to your office network
46 from home or during travel. Many companies utilize Cisco 3000 VPN concentrators
47 for their VPN needs, and I am willing to bet that most Linux newbies think that
48 -they are forced to use Windows to connect to them. Well this document informs
49 +they are forced to use Windows to connect to them. Well, this document informs
50 you that connecting to a Cisco VPN is very possible and will hopefully enable
51 you to setup a working tunnel using your Gentoo workstation or laptop.
52 </p>
53 @@ -80,7 +80,7 @@
54 <li>You have Gentoo installed</li>
55 <li>You have Internet access</li>
56 <li>You want to connect to a Cisco 3000 VPN concentrator</li>
57 - <li>You know how to configure, build and install a new kernel</li>
58 + <li>You know how to configure, build, and install a new kernel</li>
59 </ul>
60
61 </body>
62 @@ -113,9 +113,9 @@
63 </pre>
64
65 <p>
66 -From the vpnc ebuild 0.4.0-r1 on, it is tested wether TUN/TAP support is
67 -enabled. If not, enable it in your kernel config either as module or built-in,
68 -recompile and reboot.
69 +Starting with version 0.4.0-r1, the <c>vpnc</c> ebuild will test whether TUN/TAP
70 +support is enabled. If not, enable it in your kernel config either as module or
71 +built-in, recompile and reboot.
72 </p>
73
74 <p>
75 @@ -165,7 +165,6 @@
76 # <i>lsmod</i>
77 Module Size Used by
78 tun 7296 0
79 -nvidia 4050204 12
80 </pre>
81
82 <p>
83 @@ -277,7 +276,7 @@
84 <path>/etc/vpnc/default.conf</path> for its connection settings. If it doesn't
85 find that file, then it looks for <path>/etc/vpnc.conf</path>. This setup will
86 only address a single profile example and will use the configuration file
87 -location <path>/etc/vpnc.conf</path>. Make sure you do not have a
88 +location <path>/etc/vpnc.conf</path>. Make sure you do <e>not</e> have a
89 <path>/etc/vpnc/default.conf</path> file.
90 </p>
91
92 @@ -294,11 +293,11 @@
93 appropriate values for your setup. The gateway option
94 <c>vpngateway.domain.org</c> can be a fully qualified domain name or an IP
95 address. The ID and secret options should be given to you by a network
96 -administrator. If they are hesitant about giving you this info and you
97 -currently have a working setup on a Windows box which utilizes the official
98 -Cisco VPN client, then all you have to do is export your profile. The user name
99 -and password options are for your normal network sign-on, such as a Windows NT
100 -domain account.
101 +administrator. If you cannot obtain this information but you currently have a
102 +working setup on a Windows box which utilizes the official Cisco VPN client,
103 +then all you have to do is export your profile. The user name and password
104 +options are for your normal network sign-on, such as a Windows NT domain
105 +account.
106 </p>
107
108 <p>
109 @@ -463,7 +462,7 @@
110 <li>
111 A routing setup that will only send traffic destined for the VPN down the
112 virtual tunnel. This way, you can browse the Internet while connected to
113 - the VPN, without your personal web/p2p etc ... traffic going across the
114 + the VPN, without your personal web/p2p etc. traffic going across the
115 tunnel.
116 </li>
117 <li>
118 @@ -592,7 +591,7 @@
119 order to fix this situation you need to know what networks are available to you
120 on your VPN. The easiest way to find out the needed information is to ask a
121 network administrator, but sometimes they are reluctant to answer such
122 -questions. If your local network admin wont provide the needed information,
123 +questions. If your local network admin won't provide the needed information,
124 some trial and error experiments will be required.
125 </p>
126
127 @@ -766,7 +765,7 @@
128 </p>
129
130 <p>
131 -If you need to connect to a windows machine which doesn't have a DNS entry, and
132 +If you need to connect to a Windows machine which doesn't have a DNS entry, and
133 you know the address of an available WINS server, you can use a tool called
134 <c>nmblookup</c> to query the WINS server for the host name of the machine you
135 want to connect to. Unfortunately, you have to install samba to get it, but if
136
137
138
139 1.187 xml/htdocs/doc/en/metadoc.xml
140
141 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/metadoc.xml?rev=1.187&view=markup
142 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/metadoc.xml?rev=1.187&content-type=text/plain
143 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/metadoc.xml?r1=1.186&r2=1.187
144
145 Index: metadoc.xml
146 ===================================================================
147 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v
148 retrieving revision 1.186
149 retrieving revision 1.187
150 diff -u -r1.186 -r1.187
151 --- metadoc.xml 27 Jun 2007 13:31:32 -0000 1.186
152 +++ metadoc.xml 27 Jun 2007 20:18:57 -0000 1.187
153 @@ -1,9 +1,9 @@
154 <?xml version="1.0" encoding="UTF-8"?>
155 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v 1.186 2007/06/27 13:31:32 neysx Exp $ -->
156 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v 1.187 2007/06/27 20:18:57 nightmorph Exp $ -->
157 <!DOCTYPE metadoc SYSTEM "/dtd/metadoc.dtd">
158
159 <metadoc lang="en">
160 -<version>1.109</version>
161 +<version>1.110</version>
162 <members>
163 <lead>neysx</lead>
164 <member>cam</member>
165 @@ -397,6 +397,7 @@
166 <file id="change-chost">/doc/en/change-chost.xml</file>
167 <file id="xfce-config">/doc/en/xfce-config.xml</file>
168 <file id="gcc-optimization">/doc/en/gcc-optimization.xml</file>
169 + <file id="vpnc-howto">/doc/en/vpnc-howto.xml</file>
170 <file id="qa-autofailure">/proj/en/qa/autofailure.xml</file>
171 <file id="qa-automagic">/proj/en/qa/automagic.xml</file>
172 <file id="qa-backtraces">/proj/en/qa/backtraces.xml</file>
173 @@ -1264,6 +1265,10 @@
174 <memberof>sysadmin_specific</memberof>
175 <fileid>jffnms</fileid>
176 </doc>
177 + <doc id="vpnc-howto">
178 + <memberof>sysadmin_specific</memberof>
179 + <fileid>vpnc-howto</fileid>
180 + </doc>
181 <doc id="conky">
182 <memberof>desktop_config</memberof>
183 <fileid>conky</fileid>
184
185
186
187 --
188 gentoo-doc-cvs@g.o mailing list