File: README.Debian

package info (click to toggle)
wanpipe 2.1.1-2.1
  • links: PTS
  • area: main
  • in suites: woody
  • size: 1,348 kB
  • ctags: 713
  • sloc: ansic: 6,182; sh: 2,522; cpp: 2,488; makefile: 116
file content (169 lines) | stat: -rw-r--r-- 7,200 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
wanpipe for Debian
------------------

new for 2.1.1-1
===============

There are lots of changes for 2.1.1-1, so please read this carefully.

- THE NAME OF THE DEVICE CONFIGURATION FILE HAS CHANGED!!!
  Instead of /etc/wanpipe/router.conf, the default file is now
  /etc/wanpipe/$device.conf, where $device is wanpipe1, wanpipe2, etc.
  (Gripe at Sangoma if this doesn't suite you.)
  
  In the "configure" stage of installation, a link from wanpipe1.conf
  to router.conf will be created if none exists.
  
  The sample configuration files in /usr/share/doc/wanpipe/examples have
  also changed names - the extension corresponds to the protocol you want
  to run - but you still need to rename the file $device.conf in
  /etc/wanpipe.

- Support for S514 cards is included.

- There is no longer a need for the wrapper script since the wanpipe
  "pipemon" commands have been improved to accept the interface name on
  the command-line.
  
- The 2.2.14 kernel automagically synced up with the upstream patches,
  so there is no need to patch your kernel and recompile.  For that
  reason, patches are no longer distributed with the Debian package.  See
  README.patches for more information.

- It is simply too much work (for me, anyway) to manipulate the upstream
  tarball such that it can be distributed as an .orig.tar.gz file along
  with the Debian diffs.  I'll be working with Sangoma to rectify this.
  
- The upstream source no longer contains any manpages; refer to
  /usr/share/doc/wanpipe/USER_MANUAL.txt.gz

- Check http://pongo.mancill.com/wanpipe for new versions, versions for
  slink, etc.  If you have something to contribute, please send it to me
  and I'll make it available to others. 

 -- tony mancill <tmancill@debian.org>, Sat, 15 Jan 2000 07:33:00 -0700  


<because so much has changed, everything below here is only relavent for
 those interested in the pre-history of the 2.1.1 version>

new for version 2.0.6-1
=======================
Not much.  The new upstream version includes a patch for 2.2.11.
See /usr/doc/wanpipe/README.patches.
 -- tony mancill <tmancill@debian.org>  Wed, 18 Aug 1999 00:02:48 -0700


new for version 2.0.5-1
=======================
Based on the new upstream version of the tarball, which incorporates
the PPP patch and the CHDLC patches Sangoma published in early August.
There is also an xpipemon executable, but it is *alpha* (I had to
edit the source so it wouldn't claim to be fpipemon.)  I also included
a dummy manpage for it.

The kernel patches are back in the package.  See 
/usr/doc/wanpipe/README.patches for details.

The entire source has been converted to using a patching system which I
borrowed from the egcs package, so if you're compiling your own from the
sources, don't be freaked out.  Any changes to the actual files in the 
Sangoma tarball are represented in debian/patches/*.dpatch.  Files which
don't exist in the Debian package or are renamed, are still handled
in debian/rules.

Have fun, and let me know if you have problems.

If you're new to wanpipe, don't miss the "Differences" portion of this
readme a few lines down.  It highlights the differences between the 
Debian package and the Sangoma version of the software.

--------------------------------------------------------------------------

new for version 2.0.4-5
=======================
This package is compiled against the 2.2.10 kernel and with glibc2.1.  It is
intended for use on Debian 2.2 (potato) systems.  If you need other versions
(older or newer), see ftp://ftp.sangoma.com/linux/debian/.  If you have problems
getting the packages you need, please email me at <tmancill@debian.org>.

The kernel patches are no longer distributed with the package, since the 2.2.x
source tree contains the WANPIPE code.  Still, you need to read README.patches
in the /usr/doc/wanpipe directory for any special instructions.

The wanpipe kernel drivers are being integrated into the Debian kernel package,
which will mean no more patches OR kernel compiles.  More on this to follow.

new for version 2.0.4-4
=======================
+ /usr/sbin/?pipemon is now a symbolic link to /usr/sbin/pipemon_wrapper.sh
  This script allows you to use the wanpipe interface names (e.g. wan0
  instead of the dotted-ip address when you use
  fpipemon/ppipemon/cpipemon.

+ Nenad Corbic at Sangoma has re-written the user manual, which can be
  found in /usr/doc/wanpipe/USER_MANUAL.txt.  The router.txt and 
  wanpipe.txt files are no longer included.

+ example configuration files for each type of wanpipe router are now
  in /usr/doc/wanpipe/examples

+ cfgft1 will not start if wanpipe has been started.  This is for your
  own protection.

=========================================================================

Differences between the Debian package and what is described in the 
documentation from Sangoma (or distributed in the Sangoma tarball):

+ references to "router" have been changed to "wanpipe" where feasible,
  including the following:

   + /usr/sbin/router is now /usr/sbin/wanpipe
   + /usr/lib/router/Configure is now /usr/sbin/wanpipeconfig
   + /etc/router.rc is /etc/wanpipe/router.rc
   + /etc/router.conf is /etc/wanpipe/router.conf
   + /usr/lib/router/interfaces/ is now /etc/wanpipe/interfaces/
   + firmware is stored in /usr/lib/wanpipe
   + an /etc/init.d/wanpipe startup script has been included

+ The package already does all that the "Setup" script did for you 
  (except for the kernel patching); therefore this script is not provided.  

+ the /usr/doc/wanpipe/examples/apply_patches script can be run to 
  install the patches (in /usr/doc/wanpipe/patches)

+ the source code for the cfgft1 utility is included and can be found 
  in the Debian source package.

+ a patch containing an error handler when working with Cisco routers
on frame-relay links has been submitted by <marc@bard.org.il> and 
included in /usr/doc/wanpipe/patches.  Please see the README.patches
file for more details.

tony mancill <tmancill@debian.org>, Fri,  9 Jul 1999 23:58:29 -0400

=========================================================================

Some Gotchas:
-------------
1. You need to run routed AFTER you start up the router via
   /etc/init.d/wanpipe start. Otherwise the RIP information will not be 
   spread across the WAN link. The priority of the init-script installed by
   this package was adjusted so that the WAN link comes up before the
   netstd scripts and thus before the routed is started.

2. You might want to modify the invocation of routed so that information
   is broadcast to all interfaces. Remove the -q option from
   /etc/init.d/netstd_init. If the router will be the only way out to the
   Internet for your organization invoke routed with the -g option so that all
   your hosts know that this is your gateway. In that case you also need to
   find some way to add a default route via the WAN link after the router is
   started (add a script at level 19 or so).

   Note that some providers will stop routing traffic to you if you do not
   broadcast your routes to them via RIP.

Christoph Lamenter <christoph@lamenter.com>

==============================================================================