From: Forrest Kenney [kenney@star.zko.dec.doom]
Sent: Thursday, July 08, 1999 12:13 PM
To: Info-VAX@Mvb.Saic.Com
Subject: Re: Problems using PPPD on PWS 433au



Jon Morgan wrote:

> The modem DOES work (I use it to dial into work if there is a
> problem), but I just can't get PPP working using the serial port
> (TTB0: -- its the second serial port on that system). The serial port
> is set up using:
>
>         $ SET TERMINAL /PERMANANT /SPEED=28800 /MODEM /EIGHTBIT -
>         _$ /ALTYPEAHD /DIALUP /DISCONNECT /NOHANGUP /NOHOSTSYNC -
>         _$ /NOPASTHRU /NOREADSYNCH /NOTTSYNCH /TYPE_AHEAD TTB0:
>
> I have TTDRIVER and ASNDRIVER loaded and configured properly (I
> think).If I then try to setup the interface using:
>
>         $ TCPIP SET INTERFACE PP0 /SERIAL_DEVICE=TTB0:
>
> (The IP address is dynamically allocated, so I cannot use the /HOST=
> qualifier.)
>
> I get an error about the device does not exist. However, if I enter:
>
>         $ TCPIP LIST INTERFACE PP0
>
> its there. The device is also in the TCPIP LIST COMMUNICATIONS list.
>
> So, the question is how do I get TCPIP to work out that the PP0 device
> exists? If I use PPPD DIAL_OUT I can log into my ISP, but I can't get
> OpenVMS to bring up the connection, which seems fair enough because
> the interface isn't there. Am I doing something completely and utterly
>
> wrong? I would have thought that someone else would have got this to
> work, so if anyone has any ideas, I'd be grateful.
>

    I will assume that you tell your ISP  what it needs to bring up a PPP
connection,
and that you are telling PPPD to switch the line.  You should seem some of
what
looks like line noise.  This is the PPP negotiation packet from your ISP.
Then tell
PPPD to switch.

    Use the following undocumented commands to help sort out what is going
on.

pppd> set /trace=foo.trace/full ttb0:
pppd> dial ttb0


pppd> exit


pppd> convert foo.tace session_trace.txt
pppd> exit

    The session_trace.txt has beak out of the attempt to set up the link.
You can
mail that to me kenney@star.zko.dec.com.  I will look at it and send you
an
explaination of what is going worng.  Typical problems are:

    1) Remote host is insisting on using CHAP or PAP we don't support
these.
    2) Remote host is insisting on MTU/MRU larger than 1500 we don't
accept
        larger values than 1500.  There is a bug where we don't always do
the correct
        thing and try and use larger than 1500 and don't report a useful
error.  There is
        supposed to be a patch being issued for that one.
    3) Remote host insist on hardware flow control.  You can change our
end to use
        hardware flow control.  Use the set command.

    I am the resident expert on the PPP code I lead the effort to get it
on VMS.


Forrest Kenney
kenney@star.zko.dec.com
VMS Development group CompaQ