I had machines servicing dial-in users for quite a while.  A
few pointers:

	o You have to use "local".  There is no CD line (Carrier Detect)
	on the serial ports, so pppd can't tell when the modem
	has "answered".  It can only listen to the data
	coming in.

	o pppd behaves differently (I don't remember exactly how)
	when it has an "init" script, in ways that are not
	quite what you expect.  Given the above,  I would
	not bother with the init script.

	o I found that pppd can detect a dialup without any
	"support" (connect, disconnect, etc).  However, I
	had trouble from time to time where the modem
	got stuck at a different serial speed than the serial line.
	The "auto-baud" modem needs a return char, I think, to 
	figure out the speed.

	o Make sure that the "echo" is OFF on the modem.
	I put this in in the powerup NVRAM instead of
	trying to ensure that the modem got an init string
	from the serial line.

I never tried dial-out/demand.

Good luck,

-dgl-

>I can't find any documentation on setting up pppd to answer incoming calls. I've set up outgoing calls with NAT routing okay.
>
>Here's what I have to answer calls on my second modem connected to the printer port (the modem port is used for ppp nat dial out):
>
>netbsd# cat peers/answer
>
>init 'chat -f /etc/ppp/chat/answer'
>192.168.1.254:192.168.1.56
>passive
>tty01
>persist
>logfile /var/log/pppanswer
>
>
>netbsd# cat chat/answer
>ABORT   BUSY
>ABORT   "NO CARRIER"
>ABORT   "NO DIAL"
>TIMEOUT 10
>""      AT
>OK      ATZ
>OK      at&f&d0s0=2
>
>Then I issue:
>
>pppd call answer
>
>which sets up the modem okay and it answers calls. But the log doesn't tell me who called (ie which user in pap-secrets is matched) and I'm not sure whether i need to adjust ipf.conf etc.
>
>For extra points, can anyone suggest how to configure pppd to answer incoming calls or dial out on demand, whichever comes first?
>
>Thanks,
>Tom