| 1 |
nightmorph 10/07/21 01:10:47 |
| 2 |
|
| 3 |
Modified: vpnc-howto.xml |
| 4 |
Log: |
| 5 |
update kernel configuration, misc guidexml fixes, reported by tanderson on IRC |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.9 xml/htdocs/doc/en/vpnc-howto.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/vpnc-howto.xml?rev=1.9&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/vpnc-howto.xml?rev=1.9&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/vpnc-howto.xml?r1=1.8&r2=1.9 |
| 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.8 |
| 18 |
retrieving revision 1.9 |
| 19 |
diff -u -r1.8 -r1.9 |
| 20 |
--- vpnc-howto.xml 29 Nov 2008 00:03:23 -0000 1.8 |
| 21 |
+++ vpnc-howto.xml 21 Jul 2010 01:10:47 -0000 1.9 |
| 22 |
@@ -1,9 +1,8 @@ |
| 23 |
<?xml version='1.0' encoding='UTF-8'?> |
| 24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vpnc-howto.xml,v 1.8 2008/11/29 00:03:23 nightmorph Exp $ --> |
| 25 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/vpnc-howto.xml,v 1.9 2010/07/21 01:10:47 nightmorph Exp $ --> |
| 27 |
|
| 28 |
-<guide link="/doc/en/vpnc-howto.xml"> |
| 29 |
- |
| 30 |
+<guide> |
| 31 |
<title>Gentoo vpnc HOWTO</title> |
| 32 |
|
| 33 |
<author title="Author"> |
| 34 |
@@ -18,6 +17,9 @@ |
| 35 |
<author title="Contributor"> |
| 36 |
<mail link="fischer@××××××××××××××.de">Thomas Fischer</mail> |
| 37 |
</author> |
| 38 |
+<author title="Editor"> |
| 39 |
+ <mail link="nightmorph"/> |
| 40 |
+</author> |
| 41 |
|
| 42 |
<abstract> |
| 43 |
This document details how to connect your workstation to a Cisco VPN |
| 44 |
@@ -28,8 +30,8 @@ |
| 45 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 46 |
<license/> |
| 47 |
|
| 48 |
-<version>1.5</version> |
| 49 |
-<date>2008-01-23</date> |
| 50 |
+<version>2</version> |
| 51 |
+<date>2010-07-20</date> |
| 52 |
|
| 53 |
<chapter> |
| 54 |
<title>Introduction</title> |
| 55 |
@@ -138,7 +140,7 @@ |
| 56 |
|
| 57 |
<pre caption="Configuration location in the kernel configuration dialog"> |
| 58 |
Device Drivers ---> |
| 59 |
- Networking support ---> |
| 60 |
+ Network device support ---> |
| 61 |
[*] Universal TUN/TAP device driver support |
| 62 |
</pre> |
| 63 |
|
| 64 |
@@ -412,7 +414,6 @@ |
| 65 |
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 |
| 66 |
collisions:0 txqueuelen:500 |
| 67 |
RX bytes:60 (60.0 b) TX bytes:616 (616.0 b) |
| 68 |
- |
| 69 |
</pre> |
| 70 |
|
| 71 |
<pre caption="Sample routing modifications made by vpnc"> |
| 72 |
@@ -783,9 +784,9 @@ |
| 73 |
If you need to connect to a Windows machine which doesn't have a DNS entry, and |
| 74 |
you know the address of an available WINS server, you can use a tool called |
| 75 |
<c>nmblookup</c> to query the WINS server for the host name of the machine you |
| 76 |
-want to connect to. Unfortunately, you have to install samba to get it, but if |
| 77 |
-you are going to be working with boxes running Windows you might as well want |
| 78 |
-to install samba, because it includes several other useful tools. |
| 79 |
+want to connect to. Unfortunately, you have to install <c>samba</c> to get it, |
| 80 |
+but if you are going to be working with boxes running Windows you might as well |
| 81 |
+want to install samba, because it includes several other useful tools. |
| 82 |
</p> |
| 83 |
|
| 84 |
<pre caption="Installing samba"> |
| 85 |
@@ -810,15 +811,15 @@ |
| 86 |
<body> |
| 87 |
|
| 88 |
<p> |
| 89 |
-The custom-made scripts for the init.d file can be used to setup a user-defined |
| 90 |
-routing for the vpnc connection. The examples below show how to setup the |
| 91 |
-routing table so that only connections to 123.234.x.x are routed over the VPN |
| 92 |
-and all other connections use the default gateway. The example uses |
| 93 |
+The custom-made scripts for the <path>init.d</path> file can be used to setup a |
| 94 |
+user-defined routing for the vpnc connection. The examples below show how to |
| 95 |
+setup the routing table so that only connections to 123.234.x.x are routed over |
| 96 |
+the VPN and all other connections use the default gateway. The example uses |
| 97 |
work-preup.sh to save the current default gateway before starting vpnc (which |
| 98 |
resets the default gateway using the VPN connection). Once vpnc has been |
| 99 |
-started, work-postup.sh deletes this new default gateway, restores the old |
| 100 |
-default gateway and sets the route for all connections to 123.234.x.x to use |
| 101 |
-the vpnc connection. |
| 102 |
+started, <path>work-postup.sh</path> deletes this new default gateway, restores |
| 103 |
+the old default gateway and sets the route for all connections to 123.234.x.x to |
| 104 |
+use the vpnc connection. |
| 105 |
</p> |
| 106 |
|
| 107 |
<pre caption="/etc/vpnc/scripts.d/work-preup.sh"> |
Archives