I tend to turn off just about everything though !!!!
here is a 'working' ppp.conf (using a BitSurfr Pro on ISDN but works
with just about any modem assuming speed and init string are set OK !!)
Cheers
Phil
default:
set device /dev/cuaa0
set speed 115200
set mru 1500
set mtu 1500
set debug 0
set log 0
disable protocomp
disable vjcomp
disable pred1
disable lqr
disable chap
disable acfcomp
deny protocomp
deny vjcomp
deny pred1
deny lqr
deny chap
deny acfcomp
set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT%A2=95&D2@B0=1
OK-AT-OK \\dATDT\\T TIMEOUT 40 CONNECT"
#
# My connection
#
connection:
set phone 1234567
accept pap
set authname name
set authkey pass
set login "TIMEOUT 5"
set timeout 120
set openmode active
set ifaddr 10.0.1.1/0 10.0.1.2/0 255.255.255.0
add 0 0 10.0.1.2
> ----------
> From: Nick Johnson[SMTP:nick@corp.gulf.net]
> Sent: 14 August 1997 15:18
> To: portmaster-users@livingston.com
> Subject: FCS errors (PM3 & FreeBSD)
>
> I've noticed that with our PM3 with a connection from a FreeBSD
> machine
> (either using pppd or ij-ppp) I will encounter a stream of FCS errors
> followed by a disconnect. Each side of the connection thinks that the
>
> other side terminated the connection. This is a fairly repeatable
> situation that does *not* happen with the PM2e.
>
> Everything I know to try has failed to change this behavior at all.
> It
> also seems to show itself after a period of higher activity, but not
> always.
>
> Has anyone seen similar behavior with FreeBSD, Linux, or some other
> machine that uses pppd?
>
> Nick
>
> ---
> Nick Johnson, writer of code, fixer of modems, administrator of pops
> Gulf Coast Internet Network Engineering Team
> Check the web: http://www.gulf.net/support/network_status/
>