Thomas Pawlikaniec wrote:
> On Sun, 24 Jan 1999, David D. Shochat wrote:
>
> > I suggest that you
> > 1. Put kdebug down to 1
> > 2. Make sure your syslog.conf has daemon.debug going to a file (info
> > isn't good enough).
> > 3. Make sure that you are running chat with "-v" and pppd with debug.
> > 4. Post the resulting log file (as plain text! -- I can't imagine why
> > one would use jpeg for a log file.)
>
> I would add those hints:
>
> > [EMAIL PROTECTED] wrote:
> > > My Problem: after submitting authorisation (what seems to work) and the
> > > "connecting ppp0 <---> /dev/modem" there comes an unexpected "Modem
>
> use /dev/ttySx directly, where x is 0, 1, 2 etc dpending on your setup.
> (eg: ttyS0 is COM1 under DOS). Look at what the /dev/modem points to.
>
> > > Hangup"; "kdebug 25" shows that some data was queued, receive&send
> > > asyncmap are set to FFFFFF, and there is no "rcv" from the other side.
>
> Are you *sure* you want FFFFFF for asyncmap ? Never seen a need to do
> this, I'm even not sure it actually works! Some characters need to be
> transmitted 'as is' I believe, at least the asyncmap-escape ones, no?
>
> Maybe you actually wanted asyncmap 0 (ie. do not escape anything). Most
> systems work well like that, even though the default for PPP is a bit more
> conservative.
>
> > > (I've got the whole messages as a .jpg (120K) - for whom this is of
>
> As David said above, this is very weird, why would you use .JPG for a
> log? To make it barely readable, and viewable only in graphics mode ?!
>
> Good luck,
> TP
>
I've had this problem occassionally. Sometimes on otherwise working systems ie.
works ok one day and not the next. Rebooting the remote system has fixed the
problem. WHich leads me to believe either the modem is in a strange mode
(possible when faxing etc at the same time) or the pppd gets itself in a knot.
Rick
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
