Update direct-* example to reflect LQR on both sides.

Fix bogus loopback route.

This example shows LQR working on both sides of the loop.

etc/ppp/ppp.conf.sample

@@ -4,7 +4,7 @@
 #
 #	  Written by Toshiharu OHNO
 #
-# $Id: ppp.conf.sample,v 1.10 1997/03/13 21:24:18 brian Exp $
+# $Id: ppp.conf.sample,v 1.11 1997/03/16 00:59:08 jmg Exp $
 #
 #################################################################
 
@@ -108,10 +108,9 @@ pmdemand:
  set openmode active
 
 # Examples to connect using a null-modem cable from one machine to another.
-# The important thing here is to get the lqr packets going properly.
-# We disable them on the client side and enable them on the server side.
-# Without them enabled on the server side, we can't tell if the line's
-# dropped - there should always be carrier on a direct connection.
+# The important thing here is to allow the lqr packets on both sides.
+# Without them enabled, we can't tell if the line's dropped - there
+# should always be carrier on a direct connection.
 # Here, the server sends lqr's every 10 seconds and quits if three in a
 # row fail.
 #
@@ -121,19 +120,17 @@ direct-client:
  set dial ""
  set line /dev/cuaa0
  set sp 115200
- disable lqr
  set timeout 900
- set debug Phase
+ set debug Phase Chat LQM
  set login "TIMEOUT 5 -\\r-login:-\\r-login: ppp word: ppp HELLO"
  set ifaddr 10.0.4.2 10.0.4.1
- add 10.0.4.2 0 127.0.0.1
+ add 10.0.4.2 255.255.255.255 127.0.0.1
  
 direct-server:
  set timeout 900 10 3
  set debug Phase LQM
- enable lqr
  set ifaddr 10.0.4.1 10.0.4.2
- add 10.0.4.1 0 127.0.0.1
+ add 10.0.4.1 255.255.255.255 127.0.0.1
 
 # Example to validate incoming user with CHAP
 #  Invoke as ``ppp -direct users'' from login script. User's system name