network "hardwired" ppp authentication?

Chris Shenton (chris@absinthe.i3inc.com)
Fri, 16 May 1997 10:09:46 -0400

We've got a mix of vendor comm-servers and I want to make the PM do
PPP only with PAP authentication only. This is so that users don't try
to do scripted logins on our different equipment's prompts.

set all proto ppp
set all network dialin

Does basically this, but dumb-terminal logins see the Login:/Password
prompts. I was hoping to avoid this and just see PPP line noise.

So I tried "set all network hardwired" since the manual says this
immediately initiates PPP, and I *expected* it to start doing PAP with
the client to auth, after (?) IPCP negotiation. OK, I see PPP noise
immediately, but I get disconnected quickly after a successful LCP
negotiation. Looks like it's not doing the PAP thing after all.

Can someone explain this to me? If it won't do PAP, how is a hardwired
PPP connection useful? where does it get its local:remote addresses?
>From another "set s0 ... " type of command?

If I'm being stupid, let me know. For now I'll just stick with
"network dialin".

Thanks.