Very Computer

I've installed the diald rpm (diald 0.16) and it detects internet bound
packets and inits the modem.  And that's where my problems start.

diald doesn't seems to init the modem properly.  Where I am we still old
analgue exchanges, so modem don't detect dialtone and fail with a "NO
DIALTONE" response.
I put an &X3 (later took that down to a &X1) in the init string in the
connect script, but it didn't work.

I'm sure the modem does respond correctly to the X3 because that's what
I use when I dial out with minicom.

So it seems as tho' diald is either not reading from the file given as
the arg to connect, or is simply ignoring the init string.

please send e-mail if possible, but I'll check the ng as well.

--

Marc Nevin Daya
"REALITY.SYS corrupted - UNIVERSE halted"

MindSpring Computing

116 Broad Rd MediCentre
Broad Road
Wynberg
Cape Town

web:    www.mindspring.co.za

Ph  : +27 21 761 1000
Fax : +27 21 761 1001

Quote:> I've installed the diald rpm (diald 0.16) and it detects internet bound
> packets and inits the modem.  And that's where my problems start.

> diald doesn't seems to init the modem properly.  Where I am we still old
> analgue exchanges, so modem don't detect dialtone and fail with a "NO
> DIALTONE" response.
> I put an &X3 (later took that down to a &X1) in the init string in the
> connect script, but it didn't work.

connect /usr/lib/diald/connect

...and, of course, the script has to be executable.

Hope this helps.

trane
--
//------------------------------------------------------------
//  Our OS who art in cpu,
//  UNIX be thy name,
//  Thy programs run, thy syscalls done,
//  In Kernel as it is in user.
//  Amen.

    Marc> diald doesn't seems to init the modem properly.  Where I am
    Marc> we still old analgue exchanges, so modem don't detect
    Marc> dialtone and fail with a "NO DIALTONE" response.  I put an
    Marc> &X3 (later took that down to a &X1) in the init string in
    Marc> the connect script, but it didn't work.

You can look at the exchange between 'chat' and your modem the
following way.  Insert this line into your /etc/syslog.conf:

        *.*                     /dev/tty8

(Be sure to use TAB's, not spaces. There is a bug).
Restart syslogd. ("killall -HUP syslogd").

Start your dialling sequence.  You can now use Ctrl-Alt-F8 to view
the syslog messages produced by diald real-time; Ctrl-Alt-F7 to return
to X, or Ctrl-Alt-F1 through Ctrl-Alt-F6 to return to the
corresponding tty.

You should see what strings your chatscript produces, and how your
modem responds.  Also, if you enable the 'debug' flag in
/etc/ppp/options, you will see PPP negotiations, such as your
username and password.  For that reason, you may want to remove that
above line from /etc/syslog.conf when you have figured everything out.

-tor

Soren

i asked this before but with no response so here goes again.
I installed pppd-2.3.3-2 but when I put the demand in I get a message
that my kernel doesn't support demand dialing. i recompiled the kernel,
what stupid thing did I forget? I'm running RH5.0 w/ kernel 2.0.33

--
Ken C.
remove zz's for reply