# /etc/ppp/peers/freenet
# $Id: freenet,v 1.2 2002/04/28 14:02:24 root Exp $
 
# Use the executable or shell command specified to set up the serial line.  
# Here the default is to use the chat program to login to a remote machine
# and start ppp. The -v flag will cause chat to  log to /var/adm/messages. 
# Sensitive words in the /etc/ppp/chatscript file should be prefixed by \q 
# to stop chat writing these to the log file.
connect "/usr/sbin/chat -v -f /etc/chatscripts/freenet"

# Require the peer to authenticate itself before allowing network
# packets to be sent or received.
# Please do not disable this setting. It is expected to be standard in
# future releases of pppd. Use the call option (see manpage) to disable
# authentication for specific peers.
#auth
noauth

/dev/ttyS1

# Speed (baud, ISDN max: 38400)
38400

# Don't use the modem control lines.
#local

# Use the modem control lines.  On Ultrix, this option implies hardware
# flow control, as for the crtscts option.  (This option is not fully
# implemented.)
modem

# Add a default route to the system routing tables, using the peer as
# the gateway, when IPCP negotiation is successfully completed.  This
# entry is removed when the PPP connection is broken.
defaultroute

# Set the name of the local system for authentication purposes to <n>.
# This is a privileged option. With this option, pppd will use lines in the
# secrets files which have <n> as the second field when looking for a
# secret to use in authenticating the peer. In addition, unless overridden
# with the user option, <n> will be used as the name to send to the peer
# when authenticating the local system to the peer. (Note that pppd does
# not append the domain name to <n>.)
name freenet

#user freenet

# Set the assumed name of the remote system for authentication purposes
# to <n>.
remotename freenet

usepeerdns

# Use hardware flow control (i.e. RTS/CTS) to control the flow of data
# on the serial port.
crtscts

#debug