Date: Sun, 31 Dec 1995 09:52:52 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: andymac@bullseye.apana.org.au (Andrew MacIntyre) Cc: bugs@freebsd.org Subject: Re: 2.1.0 PPP hassles... Message-ID: <199512310852.JAA16764@uriah.heep.sax.de> In-Reply-To: <30e53d3f.bullseye@bullseye.apana.org.au> from "Andrew MacIntyre" at Dec 30, 95 11:23:09 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As Andrew MacIntyre wrote:
>
> 1. The dial chat script behaviour appears to have changed, seemingly
> requiring a terminating send string, whereas all the samples and the
> working config from the above mentioned SNAP-950726 system don't
> have/need it. I've used the string "\\c" to fill this for now.
Hmm, i'm not claiming that this hasn't changed, but i) i haven't
noticed any change myself, and ii) the only diff between 2.0.5 and
2.1's chat.c is:
- LogPrintf(LOG_CHAT, "sending: %s\n", buff+2);
+ if (strstr(str, "\\P")) { /* Do not log the password itself. */
+ LogPrintf(LOG_CHAT, "sending: %s\n", str);
+ } else {
+ LogPrintf(LOG_CHAT, "sending: %s\n", buff+2);
+ }
> 2. Using the dial command, after the connect has been made, but before the
> login has been executed, PPP core dumps with an "illegal instruction" error.
> Upon restarting PPP, with the modem link still up, I can use "term" and
> manually log in.
That is very strange. The only know occasions for ``illegal
instruction'' traps by now are broken CPUs. No normal code should
ever be able to cause illegal instructions, since the compiler and
assembler do not generate them.
> 3. Using a manual login, after PPP reports "Packet mode.", it then
> reports "SIOCAIFADDR: File exists" netstat -r shows that the link is
> in place, but as far as the rest of the systems is concerned, the link is
> down.
This means that some of the routes PPP was going to install did still
exist, perhaps from a previous crashed invocation of PPP. (The ``File
exists'' must be translated into ``Route exists'' as far as the
routing code is concerned.)
Something is very weird with your machine, but since very many people
are using iijppp, and nobody has ever reported anything resembling
your description, i would first suspect hardware.
--
cheers, J"org
joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512310852.JAA16764>