Update of /cvsroot/leaf/doc/guide/user-bering-uclibc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv12452
Modified Files:
bucu-pppoe.xml
Log Message:
minor corrections
Index: bucu-pppoe.xml
===================================================================
RCS file: /cvsroot/leaf/doc/guide/user-bering-uclibc/bucu-pppoe.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -d -r1.8 -r1.9
*** bucu-pppoe.xml 9 May 2004 14:19:30 -0000 1.8
--- bucu-pppoe.xml 6 Jun 2004 22:37:23 -0000 1.9
***************
*** 90,129 ****
<title>Step 1: declare the ppp and pppoe packages</title>
! <para>Those two packages are provided on the standard Bering floppy disk,
! but are not activated by default.</para>
! <para>Boot a Bering floppy image. Once the LEAF menu appears get access to
! the linux shell by (q)uitting the menu. Edit the <filename>lrpkg.cfg</filename>
! (pre Bering-uClibc-2.2.0) or <filename>leaf.cfg</filename> (Bering-uClibc-2.2.0
onwards)
! file and REPLACE the dhcpcd entry by ppp,pppoe in the list of packages to
! be loaded at boot. Check the Bering-uClibc <ulink
! url="http://leaf.sourceforge.net/doc/guide/buci-install.html";>installation
! guide</ulink> to learn how to do that.</para>
! <section>
! <title>Step 2: declare the ppp and pppoe modules</title>
! <para>In order to have a PPPoE connection working, you need to have ppp
! and pppoe support enabled through the appropriate kernel modules. You also
! need to declare the driver(s) module(s) of your network card(s). In the
! following example, we assume that both ethernet interfaces are provided
! through a standard ne 2000 PCI card.</para>
! <para>All the modules which are necessary for a PPPoE connection are
! provided on the standard Bering floppy. You just need to "declare"
! them since they are not loaded by default. As far as your network cards
! are concerned, the most popular driver modules are provided in
! <filename>/lib/modules</filename> but you might need to download the one
! corresponding to your own hardware from the Bering-uClibc modules <ulink
!
url="http://cvs.sourceforge.net/viewcvs.py/leaf/bin/bering-uclibc/packages/";>download
! area</ulink>. Refer to the Bering-uClibc <ulink
! url="http://leaf.sourceforge.net/doc/guide/buci-install.html";>installation
! guide</ulink> to learn how to do that.</para>
! <para>To declare your modules, go to the LEAF Packages configuration menu
! and choose modules. Enter 1) to edit the <filename>/etc/modules</filename>
! file and enter the following information:</para>
! <screen>
# 8390 based ethernet cards
8390
--- 90,131 ----
<title>Step 1: declare the ppp and pppoe packages</title>
! <para>Those two packages are provided on the standard Bering-uClibc floppy
! disk, but are not activated by default.</para>
! <para>Boot a Bering-uClibc floppy image. Once the LEAF menu appears get
! access to the linux shell by (q)uitting the menu. Edit the
! <filename>lrpkg.cfg</filename> (pre Bering-uClibc-2.2.0) or
! <filename>leaf.cfg</filename> (Bering-uClibc-2.2.0 onwards) file and
! REPLACE the dhcpcd entry by ppp,pppoe in the list of packages to be loaded
! at boot. Check the Bering-uClibc <ulink
! url="http://leaf.sourceforge.net/doc/guide/buci-install.html";>Installation
! Guide</ulink> to learn how to do that.</para>
! <section>
! <title>Step 2: declare the ppp and pppoe modules</title>
! <para>In order to have a PPPoE connection working, you need to have ppp
! and pppoe support enabled through the appropriate kernel modules. You
! also need to declare the driver(s) module(s) of your network card(s). In
! the following example, we assume that both ethernet interfaces are
! provided through a standard ne 2000 PCI card.</para>
! <para>All the modules which are necessary for a PPPoE connection are
! provided on the standard Bering-uClibc floppy. You just need to
! "declare" them since they are not loaded by default. As far as
! your network cards are concerned, the most popular driver modules are
! provided in <filename>/lib/modules</filename> but you might need to
! download the one corresponding to your own hardware from the
! Bering-uClibc modules <ulink
!
url="http://cvs.sourceforge.net/viewcvs.py/leaf/bin/bering-uclibc/packages/";>download
! area</ulink>. Refer to the Bering-uClibc <ulink
! url="http://leaf.sourceforge.net/doc/guide/buci-lrpkg.html";>Installation
! Guide</ulink> to learn how to do that.</para>
! <para>To declare your modules, go to the LEAF Packages configuration
! menu and choose modules. Enter 1) to edit the <filename>/etc/modules</filename>
! file and enter the following information:</para>
! <screen>
# 8390 based ethernet cards
8390
***************
*** 145,185 ****
</screen>
! <important>
! <para>The <filename>/etc/modules</filename> file provided in the
! Bering-uClibc distro is already setup with those entries commented out.
! Just remove the leading # sign to activate the corresponding module.</para>
! </important>
! <para>Backup the modules.lrp package.</para>
! </section>
! <section>
! <title>Step 3: configure ppp</title>
! <para>In the normal situation, you won't have to do anything here, the
! ppp is preconfigured for the standard situation.</para>
! <para>Connection with your ISP will be handled by PPP. The <ulink
! url="http://en.tldp.org/HOWTO/PPP-HOWTO/index.html";>PPP Howto</ulink>
! document will give you very detailed information about this protocol and
! how to set-up its numerous parameters.</para>
! <para>Please refer to the <ulink
! url="http://leaf.sourceforge.net/doc/guide/bucu-ppp.html";>Serial Modem
! configuration</ulink> section of this user's guide to learn how to
! configure your ppp package.</para>
! <para>The default options provided with the ppp.lrp should work and if you
! are not familiar with ppp leave them at first. After you get a connection
! you can "fine tune" your setup.</para>
! </section>
! <section>
! <title>Step 4: Configure pppoe</title>
! <para>Through the LEAF Package configuration menu choose pppoe. The
! following menu will appear:</para>
! <screen>
pppoe configuration files
--- 147,188 ----
</screen>
! <important>
! <para>The <filename>/etc/modules</filename> file provided in the
! Bering-uClibc distro is already setup with those entries commented
! out. Just remove the leading # sign to activate the corresponding
! module.</para>
! </important>
! <para>Backup the modules.lrp package.</para>
! </section>
! <section>
! <title>Step 3: configure ppp</title>
! <para>In the normal situation, you won't have to do anything here,
! the ppp is preconfigured for the standard situation.</para>
! <para>Connection with your ISP will be handled by PPP. The <ulink
! url="http://en.tldp.org/HOWTO/PPP-HOWTO/index.html";>PPP Howto</ulink>
! document will give you very detailed information about this protocol and
! how to set-up its numerous parameters.</para>
! <para>Please refer to the <ulink
! url="http://leaf.sourceforge.net/doc/guide/bucu-ppp.html";>Serial Modem
! configuration</ulink> section of this user's guide to learn how to
! configure your ppp package.</para>
! <para>The default options provided with the ppp.lrp should work and if
! you are not familiar with ppp leave them at first. After you get a
! connection you can "fine tune" your setup.</para>
! </section>
! <section>
! <title>Step 4: Configure pppoe</title>
! <para>Through the LEAF Package configuration menu choose pppoe. The
! following menu will appear:</para>
! <screen>
pppoe configuration files
***************
*** 191,204 ****
</screen>
! <para>Entry 1) allows you to adjust the parameter of your ppp connection
! through the <filename>/etc/ppp/peers/dsl-provider</filename> file. The
! most important argument is the <emphasis>user</emphasis> parameter which
! defines your login name.</para>
! <para>Replace the field following the user statement in the
! <filename>/etc/ppp/peers/dsl-provider</filename> [ "[EMAIL PROTECTED]"
! ] by the login name provided by your ISP.</para>
! <screen>
# Configuration file for PPP, using PPP over Ethernet
# to connect to a DSL provider.
--- 194,207 ----
</screen>
! <para>Entry 1) allows you to adjust the parameter of your ppp connection
! through the <filename>/etc/ppp/peers/dsl-provider</filename> file. The
! most important argument is the <emphasis>user</emphasis> parameter which
! defines your login name.</para>
! <para>Replace the field following the user statement in the
! <filename>/etc/ppp/peers/dsl-provider</filename> [
! "[EMAIL PROTECTED]" ] by the login name provided by your ISP.</para>
! <screen>
# Configuration file for PPP, using PPP over Ethernet
# to connect to a DSL provider.
***************
*** 214,221 ****
</screen>
! <para>Through the LEAF packages configuration menu get access to ppp
! configuration. The following menu will show-up</para>
! <screen>
ppp configuration files
--- 217,224 ----
</screen>
! <para>Through the LEAF packages configuration menu get access to ppp
! configuration. The following menu will show-up</para>
! <screen>
ppp configuration files
***************
*** 231,241 ****
</screen>
! <para>Entry 5) allows you to edit the <filename>/etc/ppp/pap-secrets</filename>.
! Enter in this file the login and password provided by your ISP. Your login
! name must EXACTLY match the one given in the previous
! <filename>/etc/ppp/peers/dsl-provider</filename> file. If you have special
! characters in secret or username, you should put them in quotes</para>
! <screen>
# This is a pap-secrets file
#
--- 234,244 ----
</screen>
! <para>Entry 5) allows you to edit the
<filename>/etc/ppp/pap-secrets</filename>.
! Enter in this file the login and password provided by your ISP. Your
! login name must EXACTLY match the one given in the previous
! <filename>/etc/ppp/peers/dsl-provider</filename> file. If you have
! special characters in secret or username, you should put them in quotes</para>
! <screen>
# This is a pap-secrets file
#
***************
*** 244,258 ****
</screen>
! <para>Backup both pppoe and ppp packages.</para>
! </section>
! <section>
! <title>Step 5: configure your interfaces file</title>
! <para>Trough the LEAF configuration menu type 1 to access to the network
! configuration menu and 1 again to edit your
<filename>/etc/network/interfaces</filename>
! file. Enter the following information:</para>
! <screen>
auto lo ppp0 eth1
--- 247,261 ----
</screen>
! <para>Backup both pppoe and ppp packages.</para>
! </section>
! <section>
! <title>Step 5: configure your interfaces file</title>
! <para>Trough the LEAF configuration menu type 1 to access to the network
! configuration menu and 1 again to edit your
<filename>/etc/network/interfaces</filename>
! file. Enter the following information:</para>
! <screen>
auto lo ppp0 eth1
***************
*** 269,309 ****
</screen>
! <para>In this <filename>/etc/network/interfaces</filename> file the lo,
! ppp0 and eth1 interfaces are brought up automatically when the
! <emphasis>ifup -a</emphasis> statement is executed at boot time by the
! <filename>/etc/init.d/networking</filename> script.</para>
! <para>The "iface ppp0 inet ppp" says:</para>
! <itemizedlist>
! <listitem>
! <para>Execute the "ip link set eth0 up" command BEFORE ppp0 is
! activated (pre-up statement)</para>
! </listitem>
! <listitem>
! <para>Execute the <filename>/sbin/pon dsl-provider eth0</filename>
! script to establish the PPPoE connection. The
<filename>dsl-provider</filename>
! file used as input by <filename>/sbin/pon</filename> is provided in
! the pppoe.lrp package.</para>
! </listitem>
! </itemizedlist>
! <para>The "iface eth1 inet static" defines the internal address of
! the router.</para>
! <para>Backup the etc.lrp package.</para>
! </section>
! <section>
! <title>Step 6: configure Shorewall</title>
! <para>Through the LEAF packages configuration menu, choose shorwall and
! check the three following files:</para>
! <para>A) The <filename>interfaces</filename> file (entry 3) defines your
! interfaces. Here connection to the net goes through ppp0. So we must set:</para>
! <screen>
(...)
#ZONE INTERFACE BROADCAST OPTIONS
--- 272,313 ----
</screen>
! <para>In this <filename>/etc/network/interfaces</filename> file the lo,
! ppp0 and eth1 interfaces are brought up automatically when the
! <emphasis>ifup -a</emphasis> statement is executed at boot time by the
! <filename>/etc/init.d/networking</filename> script.</para>
! <para>The "iface ppp0 inet ppp" says:</para>
! <itemizedlist>
! <listitem>
! <para>Execute the "ip link set eth0 up" command BEFORE ppp0
! is activated (pre-up statement)</para>
! </listitem>
! <listitem>
! <para>Execute the <filename>/sbin/pon dsl-provider eth0</filename>
! script to establish the PPPoE connection. The
<filename>dsl-provider</filename>
! file used as input by <filename>/sbin/pon</filename> is provided in
! the pppoe.lrp package.</para>
! </listitem>
! </itemizedlist>
! <para>The "iface eth1 inet static" defines the internal address
! of the router.</para>
! <para>Backup the etc.lrp package.</para>
! </section>
! <section>
! <title>Step 6: configure Shorewall</title>
! <para>Through the LEAF packages configuration menu, choose shorwall and
! check the three following files:</para>
! <para>A) The <filename>interfaces</filename> file (entry 3) defines your
! interfaces. Here connection to the net goes through ppp0. So we must
! set:</para>
! <screen>
(...)
#ZONE INTERFACE BROADCAST OPTIONS
***************
*** 313,325 ****
</screen>
! <warning>
! <para>Do not forget the "-" under the BROADCAST heading for the
! net/ppp0 entry.</para>
! </warning>
! <para>B) The <filename>masq</filename> file (entry 7). With a dial-up
! modem setup it should look like:</para>
! <screen>
(...)
#INTERFACE SUBNET
--- 317,329 ----
</screen>
! <warning>
! <para>Do not forget the "-" under the BROADCAST heading for
! the net/ppp0 entry.</para>
! </warning>
! <para>B) The <filename>masq</filename> file (entry 7). With a dial-up
! modem setup it should look like:</para>
! <screen>
(...)
#INTERFACE SUBNET
***************
*** 328,335 ****
</screen>
! <para>C) You may also need to edit the <filename>config</filename> file
! (entry 12) to adjust the CLAMPMSS variable to "yes":</para>
! <screen>
(...)
# Set this variable to "Yes" or "yes" if you want the TCP "Clamp
MSS to PMTU"
--- 332,339 ----
</screen>
! <para>C) You may also need to edit the <filename>config</filename> file
! (entry 12) to adjust the CLAMPMSS variable to "yes":</para>
! <screen>
(...)
# Set this variable to "Yes" or "yes" if you want the TCP "Clamp
MSS to PMTU"
***************
*** 343,373 ****
</screen>
! <para>Backup the shorwall.lrp package.</para>
! </section>
! <section>
! <title>Step 7: reboot...</title>
! <para>Your modem connection should be established automatically. Type
! <emphasis>plog</emphasis> to check the login sequence with your ISP. If
! there is no output check the various logs in <filename>/var/log/</filename>
! to get a clue on potential problems.</para>
! </section>
! <section>
! <title>An example: a PPPoE connection with a two PCMCIA cards setup</title>
! <para>C. Hostelet is using an old laptop as a Bering-uClibc router. His
! hardware configuration consists of one HP Omnibook 3000 laptop (Pentium
! 233Mhz, 144MB Ram, CD-Rom drive module, no floppy, no HDD), one Xircom
! CEM56 Modem/ethernet PCMCIA card and one 3Com 3C589 PCMCIA card. The
! connection to the net is provided through the first PCMCIA card connected
! to an Alcatel SpeedTouch Home ethernet modem which gives him access to
! France Telecom "Netissimo" ADSL service. The connection to the
! local network is done trough the second PCMCIA card.</para>
! <para>Here is his <filename>/etc/network/interfaces</filename> file:</para>
! <screen>
auto lo
--- 347,377 ----
</screen>
! <para>Backup the shorwall.lrp package.</para>
! </section>
! <section>
! <title>Step 7: reboot...</title>
! <para>Your modem connection should be established automatically. Type
! <emphasis>plog</emphasis> to check the login sequence with your ISP. If
! there is no output check the various logs in <filename>/var/log/</filename>
! to get a clue on potential problems.</para>
! </section>
! <section>
! <title>An example: a PPPoE connection with a two PCMCIA cards setup</title>
! <para>C. Hostelet is using an old laptop as a Bering-uClibc router. His
! hardware configuration consists of one HP Omnibook 3000 laptop (Pentium
! 233Mhz, 144MB Ram, CD-Rom drive module, no floppy, no HDD), one Xircom
! CEM56 Modem/ethernet PCMCIA card and one 3Com 3C589 PCMCIA card. The
! connection to the net is provided through the first PCMCIA card
! connected to an Alcatel SpeedTouch Home ethernet modem which gives him
! access to France Telecom "Netissimo" ADSL service. The
! connection to the local network is done trough the second PCMCIA card.</para>
! <para>Here is his <filename>/etc/network/interfaces</filename> file:</para>
! <screen>
auto lo
***************
*** 392,409 ****
</screen>
! <para>Only lo is brought up automatically at boot time. eth0 and eth1 are
! brought up by the PCMCIA cardmgr program which calls the
! <filename>/etc/pcmcia/network</filename> script.</para>
! <para>The connection with the Alcatel speedtouch modem is done through the
! eth0 interface at address 10.0.0.1</para>
! <para>Once the eth0 interface is up the pppd daemon is called by the pon
! script. Shorewall must then be restarted since eth0 was not available at
! boot time</para>
! <para>Once the eth1 interface is up we restart dnscache which could not
! start at boot time since eth1 was not available.</para>
</section>
- </section>
</chapter>
\ No newline at end of file
--- 396,413 ----
</screen>
! <para>Only lo is brought up automatically at boot time. eth0 and eth1
! are brought up by the PCMCIA cardmgr program which calls the
! <filename>/etc/pcmcia/network</filename> script.</para>
! <para>The connection with the Alcatel speedtouch modem is done through
! the eth0 interface at address 10.0.0.1</para>
! <para>Once the eth0 interface is up the pppd daemon is called by the pon
! script. Shorewall must then be restarted since eth0 was not available at
! boot time</para>
! <para>Once the eth1 interface is up we restart dnscache which could not
! start at boot time since eth1 was not available.</para>
! </section>
</section>
</chapter>
\ No newline at end of file
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Leaf-cvs-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits
