Bug 15924 - PPP don't start...the modem don't dial-up
Summary: PPP don't start...the modem don't dial-up
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ppp
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Thomas Woerner
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-08-10 14:40 UTC by Need Real Name
Modified: 2008-05-01 15:37 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2004-08-13 09:24:18 UTC


Attachments (Terms of Use)

Description Need Real Name 2000-08-10 14:40:28 UTC
With an external USR 56K ...PPP don't launch the dial up sequence.
It was running on RH 6.2.

The modem is correctly detected (Kudzu says USR 56 external/fax modem)

RedHat ppp applet (gnome) do nothing, and PPP (control panel) freeze on connect.
No sound, no lights on modem.

Perhaps a bad sequence : ATZ...

Comment 1 Nalin Dahyabhai 2000-08-18 21:12:37 UTC
The ATZ sequence resets the modem to its defaults.  What are the contents of
/etc/sysconfig/network-scripts/ifcfg-ppp0?

Comment 2 Need Real Name 2000-08-23 08:35:33 UTC
I ve found that with a another ppp dialer (vppp), the default init sequence
don't work for the USR 56 ext fax modem : Modem init : AT&F&C1&D2Q0&K3W2  

If I add Z to the sequence line...it works... :
Modem init : ATZ&F&C1&D2Q0&K3W2

contents of /etc/sysconfig/network-scripts/ifcfg-ppp0 :

DEVICE=ppp0
NAME=clubint
WVDIALSECT=clubint
MODEMPORT=/dev/ttyS0
LINESPEED=57600
PAPNAME=clubint/bvasta
USERCTL=true
ONBOOT=no
PERSIST=no

In which file can I found the init sequence used by redHat ppp apllet ?
I think it just that...

bruno@infodia.fr

Comment 3 Nalin Dahyabhai 2000-08-23 09:57:45 UTC
The init string is saved to /etc/wvdial.conf, to the appropriate "Modem"
section.

Comment 4 Thomas Woerner 2004-08-13 09:24:18 UTC
Please verify this with a newer version of Red Hat Enterprise Linux or Fedora
Core and reopen it against the new version if it still occurs.

Closing as "not a bug" for now.



Note You need to log in before you can comment on or make changes to this bug.