pppd: Fix SIGSEGV in EAP-TLS code when TLS verify method is not specified

[ppp.git] / README.pppoe

diff --git a/README.pppoe b/README.pppoe
index 5284e4da6863bc05adec59e504ed5a4bdde3823f..2909e1310a31f23f62719bc97cd0538084240704 100644 (file)
--- a/README.pppoe
+++ b/README.pppoe
@@ -33,7 +33,7 @@ received from the PPPoE layer just as if the link was a serial line
 
 With this in mind, the goal of the implementation of PPPoE support in
 Linux is to allow users to simply specify that the device they intend
 
 With this in mind, the goal of the implementation of PPPoE support in
 Linux is to allow users to simply specify that the device they intend

-to use for the PPP connection is an ethernet device (i.e. "eth0") and
+to use for the PPP connection is an ethernet device (e.g. "eth0") and

 the rest of the system should function as usual.
 
 2. Using PPPoE
 the rest of the system should function as usual.
 
 2. Using PPPoE


@@ -52,7 +52,7 @@ to connect to their ISP who is providing PPPoE based services.
 
 4.  Add the following line to /etc/ppp/options:
 
 
 4.  Add the following line to /etc/ppp/options:
 

-    plugin rp-pppoe.so
+    plugin pppoe.so

 
     The effect of this line is simply to make "eth0", "eth1",
     ....,"ethx" all valid device names for pppd (just like ttyS0,
 
     The effect of this line is simply to make "eth0", "eth1",
     ....,"ethx" all valid device names for pppd (just like ttyS0,