I finally got ppp to launch and connect but now, even though I followed
all of the steps in the how to, I am unable to have my ip routed.  When I
do a netstat -i it only talks about the ae0 devices and not about ppp.
Let me clarify.  The ae0 ends up getting an address while the ppp0 and
ppp1 stay with the <link> next to them.  What could be happening?  Do I
have to specify my internal network nodes?  Where do I do that at since it
wasn't in the ip-nat howto?  I am using 193.1.1.1-193.1.1.22 for my LAN
ips.  Anyone know if that could be mucking it up.  It just still looks
like something is wrong with the ppp connection.

Thanks,

Paul

"Intel Inside"...The world's most widely used warning label."

"Mac users often swear by their Macs, whereas PC users often swear at 
their PCs."
-----------------------------------------------------------------
   'At times we must engage an act of faith that
    key things are doable that are not provable' -- Bob Galvin
-----------------------------------------------------------------

On Tue, 14 Jul 1998, Michael G. Schabert wrote:

> >THe problem goes further then that.  I have an account with Primenet and
> >when you login via ppp you have to have pri/Ppatriot in the login field.
> >I wonder if that is causing a problem.  I have my login script saying
> >s/\$LOGIN/pri/Plogin/g
> >s/\$PASSWD/password/g
> >with "login" being my real login and the password being my real password
> >(didn't want to send them out to everybody ;P
> 
> I think that you're misunderstanding exactly what the ppp-login file is
> for. It's not a "script", but rather it's a token replacement. You really
> want to put the pri/P part in your ppp-chat script. Your chat script should
> look something like this:
> 
> 
> =========
> ABORT BUSY
> ABORT "NO CARRIER"
> ABORT "NO DIAL"
> TIMEOUT 10
> "" ATZ OK AT&F1m0
> OK ATDT$NUMBER
> TIMEOUT 60
> CONNECT ""
> ogin:--ogin: pri/P$LOGIN
> word: $PASSWD
> =========
> 
> 
> Hope this helps,
> Mike
> 
> Bikers don't *DO* taglines.
> 
> 
>