LinuxQuestions.org - Help configure a winmodem

- Linux From Scratch (https://www.linuxquestions.org/questions/linux-from-scratch-13/)

- - Help configure a winmodem (https://www.linuxquestions.org/questions/linux-from-scratch-13/help-configure-a-winmodem-506361/)

Help configure a winmodem

Well, I don't like to open new threads when there are lots of "similar" threads around, but ...
I have an internal Conexant modem [winmodem]. I installed a driver for it in both my FC3 and my LFS. I am able to dial-up from my FC3 [no questions - it's just perfect], which means the modem is ok and its driver is ok.
Now step by step:
I know I have a module device in /dev - it's ttyHSFS0.
I know kernel modules for my modem get loaded.
I know I have all necessary software compiled and installed - since I could install "wvdial", it has all dependencies.
I can make wvdial dial my ISP, but after username and password check it says "authentification failed".
Wvdial info/man files say after it dials the ISP, it hands it to "pppd".
"pppstats" returns "no ppp devices found".
I think I could solve this by "imitating" my FC3, but
I don't know how FC3 dials up.
I'd be very greatful if there is someone to tell me what to do [or even better - where/what to search].

Vitalie CIUBOTARU

I do know what modem I am using:

Quote:

I have an internal Conexant modem [winmodem]

Actually, its a "Conexant HSF Churchill Data/Fax" modem (PCI card). The driver I am using is "hsfmodem-7.18.00.07".

Since you said you got the "authentification failed" message, that makes me wonder ¿which protocol are you using to connect? and ¿is that protocol (chap / pap / plain text password) you have selected, _supported_ by your ISP? If you show your config and connection logs you can get a better answer. Anyway, sometimes you have to comment out some line in /etc/ppp/options, to look like "#lock", or change "auth" by "noauth" in some other cases.

I have a Conexant, but I don't use it. I'm currently using my 536ep. I never could get wvdial to do its thing either. Maybe it was just me. Try pppd/chat combo. It's not hard, and there's even a setup script for the whole thing:

ftp://sunsite.unc.edu:/pub/Linux/sys...rk/serial/ppp/

and download pppsetup. If nothing else that will give you handy ppp-on, ppp-off script to link up the interface with. I like it because it only uses pppd and chat. You might want to symlink your modem device to /dev/modem if you didn't do that already, most things look there.

The setup scripts just fill out your /etc/ppp/options file for pppd, and make a chat script in /etc/ppp/. Looks like this running:

/usr/sbin/pppd -detach connect /usr/sbin/chat -v -f /etc/ppp/pppscript

When you want the link, you just do "ppp-on". "ppp-off" downs it again.

Code:

>ip addr show



20: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 3 link/ppp inet 64.179.12.17 peer 66.202.18.61/32 scope global ppp0

On that same server there's a bunch of other ppp programs too. Probably what is happening is your ISP is using a method of auth you're not prepared for or using. Could be chap, pap, mschap, etc. Mine was pap.

Code:

# General configuration options for PPPD:

lock

defaultroute

noipdefault

modem

/dev/modem

# speed 9600 +19200 38400 *57600 (nope -> )76800 (not supported? ->) 96000

57600

crtscts

# Uncomment the line below for more verbose error reporting:

debug

# This may NOT work 9-15 is valid

#deflate 10

# If you have a default route already, pppd may require the other side

# to authenticate itself, which most ISPs will not do.  To work around this,

# uncomment the line below.  Note that this may have negative side effects

# on system security if you allow PPP dialins.  See the docs in /usr/doc/ppp*

# for more information.

#noauth

passive

asyncmap 0

name "my-login-name"