Dialin to Fedora Core 3 from Windows

(config and log files below)
I can't get this to work. I've tried 2 different modems and the behavior
is different. With both from the windows side it connects You get the
"Verifying username and password" window and then about 20 sec. later get
the "Error: 721 Remote computer not responding. etc..." window. On the
linux side the behavior is different (the mgetty logs are below). With a
Best Data modem the pppd is started and stays running until manually
killed. With a USR modem it appears the pppd is never started and the
mgetty is restarted by init. Any ideas appreciated.

Config files:

/etc/ppp/options:
auth
-chap
+pap
login
idle 300
modem
crtscts
ipcp-accept-local
ipcp-accept-remote
debug
proxyarp
lock
netmask 255.255.255.0

/etc/ppp/options.ttyS0:
192.168.1.2:192.168.1.3

/etc/ppp/pap-secrets:
# Secrets for authentication using PAP
# client server secret IP addresses
####### redhat-config-network will overwrite this part!!! (begin) ##########
####### redhat-config-network will overwrite this part!!! (end) ############
hypercare * p4sswd 192.168.1.50
freshome * p4sswd 192.168.1.50

/etc/mgetty+sendfax/login.config:
# login.config
#
# This is a sample "login dispatcher" configuration file for mgetty
#
# Format:
# username userid utmp_entry login_program [arguments]
#
# Meaning:
# for a "username" entered at mgettys login: prompt, call
# "login_program" with [arguments], with the uid set to "userid",
# and a USER_PROCESS utmp entry with ut_user = "utmp_entry"
#
# username may be prefixed / suffixed by "*" (wildcard)
#
# Automatic PPP startup on receipt of LCP configure request (AutoPPP).
# mgetty has to be compiled with "-DAUTO_PPP" for this to work.
# Warning: Case is significant, AUTOPPP or autoppp won't work!
# Consult the "pppd" man page to find pppd options that work for you.
#
# NOTE: for *some* users, the "-detach" option has been necessary, for
# others, not at all. If your pppd doesn't die after hangup, try it.
#
# NOTE2: "debug" creates lots of debugging info. LOOK AT IT if things
# do not work out of the box, most likely it's a ppp problem!
#
# NOTE3: "man pppd" is your friend!
#
# NOTE4: max. 9 arguments allowed.
#
/AutoPPP/ - a_ppp /usr/sbin/pppd auth -chap +pap login debug
#/AutoPPP/ - - /usr/sbin/pppd

#
#
# An example where no login name in the argument list is desired:
# automatically telnetting to machine "smarty" for a given login name
#
#telnet-smarty gast telnet /usr/bin/telnet -8 smarty
#
# This is the "standard" behaviour - *dont* set a userid or utmp
# entry here, otherwise /bin/login will fail!
# This entry isn't really necessary: if it's missing, the built-in
# default will do exactly this.
#
* - - /bin/login @

mgetty log Best Data:

03/17 15:57:52 yS0 wfr: waiting for ``RING''
03/17 15:57:52 yS0 send: ATA[0d]
03/17 15:57:52 yS0 waiting for ``CONNECT'' ** found **
03/17 15:58:11 yS0 send:
03/17 15:58:11 yS0 waiting for ``_'' ** found **
03/17 15:58:13 yS0 WARNING: starting login while DCD is low!
03/17 15:58:13 ##### data dev=ttyS0, pid=4817, caller='none', conn='38400', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'

mgetty log USR:
--
03/17 16:20:16 yS0 mgetty: experimental test release 1.1.31-Jul24
03/17 16:20:16 yS0 check for lockfiles
03/17 16:20:16 yS0 locking the line
03/17 16:20:17 yS0 WARNING: DSR is off - modem turned off or bad cable?
03/17 16:20:17 yS0 lowering DTR to reset Modem
03/17 16:20:18 yS0 send: \dATQ0V1H0[0d]
03/17 16:20:18 yS0 waiting for ``OK'' ** found **
03/17 16:20:18 yS0 send: ATS0=0Q0&D3&C1[0d]
03/17 16:20:18 yS0 waiting for ``OK'' ** found **
03/17 16:20:18 yS0 mdm_send: 'ATI'
03/17 16:20:19 yS0 USR Courier/Sportster 56k detected
03/17 16:20:19 yS0 mdm_send: 'ATI3'
03/17 16:20:19 yS0 additional info: 'U.S. Robotics 56K FAX EXT V5.1.4'
03/17 16:20:19 yS0 modem quirks: 0080
03/17 16:20:19 yS0 mdm_send: 'AT+FCLASS=2.0' -> OK
03/17 16:20:19 yS0 mdm_send: 'AT+FAA=1;+FCR=1' -> OK
03/17 16:20:19 yS0 mdm_send: 'AT+FBO=1' -> OK
03/17 16:20:19 yS0 mdm_send: 'AT+FNR=1,1,1,0' -> OK
03/17 16:20:20 yS0 mdm_send: 'AT+FLI="49 115 xxxxxxxx"' -> OK
03/17 16:20:20 yS0 mdm_send: 'AT+FCC=1,5,0,2,0,0,0,0' -> OK
03/17 16:20:20 yS0 waiting...
03/17 16:22:07 yS0 wfr: waiting for ``RING''
03/17 16:22:07 yS0 send: ATA[0d]
03/17 16:22:07 yS0 waiting for ``CONNECT'' ** found **
03/17 16:22:17 yS0 send:
03/17 16:22:17 yS0 waiting for ``_'' ** found **
03/17 16:22:19 yS0 clean_line: only 500 of 2308 bytes logged
03/17 16:23:01 ##### failed dev=ttyS0, pid=5685, got signal 1, exiting

--
messages:

Mar 17 15:58:13 new-host mgetty[4817]: data dev=ttyS0, pid=4817, caller='none', conn='38400', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'
Mar 17 15:58:14 new-host kernel: CSLIP: code copyright 1989 Regents of the University of California
Mar 17 15:58:14 new-host kernel: PPP generic driver version 2.4.2
Mar 17 15:58:14 new-host pppd[4817]: pppd 2.4.2 started by a_ppp, uid 0
Mar 17 15:59:12 new-host ntpd[4201]: kernel time sync enabled 0001



Log files:

On Thu, 17 Mar 2005 16:50:36 -0600, Ron Albright wrote:

> (config and log files below)
> I can't get this to work. I've tried 2 different modems and the behavior
> is different. With both from the windows side it connects You get the
> "Verifying username and password" window and then about 20 sec. later get
> the "Error: 721 Remote computer not responding. etc..." window. On the
> linux side the behavior is different (the mgetty logs are below). With a
> Best Data modem the pppd is started and stays running until manually
> killed. With a USR modem it appears the pppd is never started and the
> mgetty is restarted by init. Any ideas appreciated.

To followup on my own post, I pulled the phone cord from the linux modem
and plugged it into an old redhat 7.3 box and using the exact same dialup
connection from the windows side connected with no problems.

>
> Config files:
>
> /etc/ppp/options:
> auth
> -chap
> +pap
> login
> idle 300
> modem
> crtscts
> ipcp-accept-local
> ipcp-accept-remote
> debug
> proxyarp
> lock
> netmask 255.255.255.0
>
> /etc/ppp/options.ttyS0:
> 192.168.1.2:192.168.1.3
>
> /etc/ppp/pap-secrets:
> # Secrets for authentication using PAP
> # client server secret IP addresses
> ####### redhat-config-network will overwrite this part!!! (begin) ##########
> ####### redhat-config-network will overwrite this part!!! (end) ############
> hypercare * p4sswd 192.168.1.50
> freshome * p4sswd 192.168.1.50
>
> /etc/mgetty+sendfax/login.config:
> # login.config
> #
> # This is a sample "login dispatcher" configuration file for mgetty
> #
> # Format:
> # username userid utmp_entry login_program [arguments]
> #
> # Meaning:
> # for a "username" entered at mgettys login: prompt, call
> # "login_program" with [arguments], with the uid set to "userid",
> # and a USER_PROCESS utmp entry with ut_user = "utmp_entry"
> #
> # username may be prefixed / suffixed by "*" (wildcard)
> #
> # Automatic PPP startup on receipt of LCP configure request (AutoPPP).
> # mgetty has to be compiled with "-DAUTO_PPP" for this to work.
> # Warning: Case is significant, AUTOPPP or autoppp won't work!
> # Consult the "pppd" man page to find pppd options that work for you.
> #
> # NOTE: for *some* users, the "-detach" option has been necessary, for
> # others, not at all. If your pppd doesn't die after hangup, try it.
> #
> # NOTE2: "debug" creates lots of debugging info. LOOK AT IT if things
> # do not work out of the box, most likely it's a ppp problem!
> #
> # NOTE3: "man pppd" is your friend!
> #
> # NOTE4: max. 9 arguments allowed.
> #
> /AutoPPP/ - a_ppp /usr/sbin/pppd auth -chap +pap login debug
> #/AutoPPP/ - - /usr/sbin/pppd
>
> #
> #
> # An example where no login name in the argument list is desired:
> # automatically telnetting to machine "smarty" for a given login name
> #
> #telnet-smarty gast telnet /usr/bin/telnet -8 smarty
> #
> # This is the "standard" behaviour - *dont* set a userid or utmp
> # entry here, otherwise /bin/login will fail!
> # This entry isn't really necessary: if it's missing, the built-in
> # default will do exactly this.
> #
> * - - /bin/login @
>
> mgetty log Best Data:
>
> 03/17 15:57:52 yS0 wfr: waiting for ``RING''
> 03/17 15:57:52 yS0 send: ATA[0d]
> 03/17 15:57:52 yS0 waiting for ``CONNECT'' ** found **
> 03/17 15:58:11 yS0 send:
> 03/17 15:58:11 yS0 waiting for ``_'' ** found **
> 03/17 15:58:13 yS0 WARNING: starting login while DCD is low!
> 03/17 15:58:13 ##### data dev=ttyS0, pid=4817, caller='none', conn='38400', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'
>
> mgetty log USR:
> --
> 03/17 16:20:16 yS0 mgetty: experimental test release 1.1.31-Jul24
> 03/17 16:20:16 yS0 check for lockfiles
> 03/17 16:20:16 yS0 locking the line
> 03/17 16:20:17 yS0 WARNING: DSR is off - modem turned off or bad cable?
> 03/17 16:20:17 yS0 lowering DTR to reset Modem
> 03/17 16:20:18 yS0 send: \dATQ0V1H0[0d]
> 03/17 16:20:18 yS0 waiting for ``OK'' ** found **
> 03/17 16:20:18 yS0 send: ATS0=0Q0&D3&C1[0d]
> 03/17 16:20:18 yS0 waiting for ``OK'' ** found **
> 03/17 16:20:18 yS0 mdm_send: 'ATI'
> 03/17 16:20:19 yS0 USR Courier/Sportster 56k detected
> 03/17 16:20:19 yS0 mdm_send: 'ATI3'
> 03/17 16:20:19 yS0 additional info: 'U.S. Robotics 56K FAX EXT V5.1.4'
> 03/17 16:20:19 yS0 modem quirks: 0080
> 03/17 16:20:19 yS0 mdm_send: 'AT+FCLASS=2.0' -> OK
> 03/17 16:20:19 yS0 mdm_send: 'AT+FAA=1;+FCR=1' -> OK
> 03/17 16:20:19 yS0 mdm_send: 'AT+FBO=1' -> OK
> 03/17 16:20:19 yS0 mdm_send: 'AT+FNR=1,1,1,0' -> OK
> 03/17 16:20:20 yS0 mdm_send: 'AT+FLI="49 115 xxxxxxxx"' -> OK
> 03/17 16:20:20 yS0 mdm_send: 'AT+FCC=1,5,0,2,0,0,0,0' -> OK
> 03/17 16:20:20 yS0 waiting...
> 03/17 16:22:07 yS0 wfr: waiting for ``RING''
> 03/17 16:22:07 yS0 send: ATA[0d]
> 03/17 16:22:07 yS0 waiting for ``CONNECT'' ** found **
> 03/17 16:22:17 yS0 send:
> 03/17 16:22:17 yS0 waiting for ``_'' ** found **
> 03/17 16:22:19 yS0 clean_line: only 500 of 2308 bytes logged
> 03/17 16:23:01 ##### failed dev=ttyS0, pid=5685, got signal 1, exiting
>
> --
> messages:
>
> Mar 17 15:58:13 new-host mgetty[4817]: data dev=ttyS0, pid=4817, caller='none', conn='38400', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'
> Mar 17 15:58:14 new-host kernel: CSLIP: code copyright 1989 Regents of the University of California
> Mar 17 15:58:14 new-host kernel: PPP generic driver version 2.4.2
> Mar 17 15:58:14 new-host pppd[4817]: pppd 2.4.2 started by a_ppp, uid 0
> Mar 17 15:59:12 new-host ntpd[4201]: kernel time sync enabled 0001
>
>
>
> Log files:

Ron Albright <(E-Mail Removed)> wrote:
> On Thu, 17 Mar 2005 16:50:36 -0600, Ron Albright wrote:

>> I can't get this to work. I've tried 2 different modems and the behavior
>> is different. With both from the windows side it connects You get the
>> "Verifying username and password" window and then about 20 sec. later get
>> the "Error: 721 Remote computer not responding. etc..." window. On the
>> linux side the behavior is different (the mgetty logs are below). With a
>> Best Data modem the pppd is started and stays running until manually
>> killed. With a USR modem it appears the pppd is never started and the
>> mgetty is restarted by init. Any ideas appreciated.

> To followup on my own post, I pulled the phone cord from the linux modem
> and plugged it into an old redhat 7.3 box and using the exact same dialup
> connection from the windows side connected with no problems.

A USR Sportster usually requires AT&F1 for modem initialization.

Compare the mgetty configuration files for the box that works to those
of the other two boxes. Also the mgetty lines in /etc/inittab. Imitate
the ones on the working box except initialize the USR as suggested above.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/

On Thu, 17 Mar 2005 20:19:59 -0600, Clifford Kite wrote:

>
> A USR Sportster usually requires AT&F1 for modem initialization.
>
> Compare the mgetty configuration files for the box that works to those
> of the other two boxes. Also the mgetty lines in /etc/inittab. Imitate
> the ones on the working box except initialize the USR as suggested above.

I'll try the AT&F1. I pulled everything from inittab, /etc/mgetty+sendfax
and /etc/ppp from the working box and it didn't help. The config files I
posted were pulled from the working box. After messing extensively with
the config files it seems no matter what I do to them it has no effect. I
even tried using a wrong login username and password to see if I would get
a "invalid username or password" but it made no difference. It appears the
authentication isn't even starting. I tried pap-secrets, chap-secrets and
login authencation. I tried changing the shell for the login account to
/usr/sbin/pppd and logging in through a terminal window. The result is
the same for everything.

Ron Albright <(E-Mail Removed)> wrote:
> On Thu, 17 Mar 2005 20:19:59 -0600, Clifford Kite wrote:
>>
>> A USR Sportster usually requires AT&F1 for modem initialization.
>>
>> Compare the mgetty configuration files for the box that works to those
>> of the other two boxes. Also the mgetty lines in /etc/inittab. Imitate
>> the ones on the working box except initialize the USR as suggested above.

> I'll try the AT&F1. I pulled everything from inittab, /etc/mgetty+sendfax
> and /etc/ppp from the working box and it didn't help. The config files I
> posted were pulled from the working box. After messing extensively with
> the config files it seems no matter what I do to them it has no effect. I
> even tried using a wrong login username and password to see if I would get
> a "invalid username or password" but it made no difference. It appears the
> authentication isn't even starting. I tried pap-secrets, chap-secrets and
> login authencation. I tried changing the shell for the login account to
> /usr/sbin/pppd and logging in through a terminal window. The result is
> the same for everything.

Okay, except for the Sportster initialization, after looking more
carefully at the logs the basic problem might be hardware-related.
The Best Data modem showed

> 03/17 15:58:13 yS0 WARNING: starting login while DCD is low!

which means the serial device detects no carrier (DCD=Data Carrier
Detect). If the serial cable is the same for both boxes then this
may mean that the serial device for this box has a problem.

It might also be useful to see what happens during PPP negotiations
when using the Best Data modem. The AutoPPP line showed pppd had
the debug option, so to get a log of those just add the line below
to /etc/syslog.conf

daemon.*;local2.* /var/log/ppp.log

and get syslogd to reread that file with "killall -HUP syslogd".

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/

On Fri, 18 Mar 2005 07:41:28 -0600, Clifford Kite wrote:

> Okay, except for the Sportster initialization, after looking more
> carefully at the logs the basic problem might be hardware-related.
> The Best Data modem showed

What do I change to change the init string set to the modem? I can see
various stuff being set by mgetty but I can't find the stuff that's being
sent in any of the config files in /etc/mgetty+sendfax. I would
have guessed it was coming from /etc/mgetty+sendfax/mgetty.config but
there not in there.

>
>> 03/17 15:58:13 yS0 WARNING: starting login while DCD is low!
>
> which means the serial device detects no carrier (DCD=Data Carrier
> Detect). If the serial cable is the same for both boxes then this
> may mean that the serial device for this box has a problem.

I reconfigured things. On a RedHat 7.3 box I have a pcmcia modem as
/dev/ttyS2, the external BestData modem on /dev/ttyS1 and the external USR
on /dev/ttyS0. I can dial into the pcmcia modem with no problems. I get
the same thing as earlier when I try dialing into the ttyS0 or ttyS1. So
you're right that it has to be something in the serial port configuration
or a hardware problem. But I've tried 2 different serial cables and modems
on 4 different serial ports on 3 different computers (2 Fedora Core 3 and
a RedHat 7.3) and the result is the same. Is there something I'm missing
that has to be configured on the /dev/ttyS0 for the external modem?

>
> It might also be useful to see what happens during PPP negotiations
> when using the Best Data modem. The AutoPPP line showed pppd had
> the debug option, so to get a log of those just add the line below
> to /etc/syslog.conf
>
> daemon.*;local2.* /var/log/ppp.log
>
> and get syslogd to reread that file with "killall -HUP syslogd".

There was no logging when trying to connect through /dev/ttyS0 but a
successful session was logged when connecting through /dev/ttyS2.

Ron Albright <(E-Mail Removed)> wrote:
> On Fri, 18 Mar 2005 07:41:28 -0600, Clifford Kite wrote:

>> Okay, except for the Sportster initialization, after looking more
>> carefully at the logs the basic problem might be hardware-related.
>> The Best Data modem showed

> What do I change to change the init string set to the modem? I can see
> various stuff being set by mgetty but I can't find the stuff that's being
> sent in any of the config files in /etc/mgetty+sendfax. I would
> have guessed it was coming from /etc/mgetty+sendfax/mgetty.config but
> there not in there.

The modem initialization can be in mgetty.config using

init-chat "" <modem init1> OK <modem init2> OK ... \c

(Here mgetty+sendfax is in /usr/local/etc/ but it can probably be
elsewhere - I don't recall.)

It can also be in inittab with the -m parameter, e.g.,

d3:2:respawn:/usr/local/sbin/mgetty -D -n 2 -s 38400 -m '"" ATZ OK AT\&F
OK AT\#CID=1S0=0 OK \c' ttyS1

(I used this with additional configuration in dialin.config to defend
against telemarketers before No Call lists came into being.)

>>> 03/17 15:58:13 yS0 WARNING: starting login while DCD is low!
>>
>> which means the serial device detects no carrier (DCD=Data Carrier
>> Detect). If the serial cable is the same for both boxes then this
>> may mean that the serial device for this box has a problem.

> I reconfigured things. On a RedHat 7.3 box I have a pcmcia modem as
> /dev/ttyS2, the external BestData modem on /dev/ttyS1 and the external USR
> on /dev/ttyS0. I can dial into the pcmcia modem with no problems. I get
> the same thing as earlier when I try dialing into the ttyS0 or ttyS1. So
> you're right that it has to be something in the serial port configuration
> or a hardware problem. But I've tried 2 different serial cables and modems
> on 4 different serial ports on 3 different computers (2 Fedora Core 3 and
> a RedHat 7.3) and the result is the same. Is there something I'm missing
> that has to be configured on the /dev/ttyS0 for the external modem?

Not for the modem, for the serial device used by the modem. The serial
port (device) connectors on the computer should be identified as 1,2,3,4
(where 3 and 4 may not exist). These very likely use IRQs and ports
as detailed in "man setserial". "setserial /dev/ttySx" will show the
IRQ, port, and UART configured for ttySx which must match the serial
device's, e.g,

~# setserial /dev/ttyS1
/dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3

If there is no serial device available for a device file then the UART
is shown as "unknown," e.g.,

~# setserial /dev/ttyS2
/dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4

The PCMCIA modem using ttyS2 likely has a built-in serial device
that uses a port and IRQ different from those shown for ttyS2 in
"man setserial." Note that a modem's serial device IRQ should not
be used by anything else. Check with "cat /proc/interrupts".

>> It might also be useful to see what happens during PPP negotiations
>> when using the Best Data modem. The AutoPPP line showed pppd had
>> the debug option, so to get a log of those just add the line below
>> to /etc/syslog.conf
>>
>> daemon.*;local2.* /var/log/ppp.log
>>
>> and get syslogd to reread that file with "killall -HUP syslogd".

> There was no logging when trying to connect through /dev/ttyS0 but a
> successful session was logged when connecting through /dev/ttyS2.

I think this means that there were no log messages when using the Best
Data modem while the PCMCIA modem allowed a successful PPP connection.
Since pppd started with the Best Data that seems peculiar. Well, not
so strange after all since I thought the actual pppd command line would
have the debug option as shown in the /AutoPPP/ line of login.conf from
your first post, but apparently does not (cmd):

> 03/17 15:58:13 ##### data dev=ttyS0, pid=4817, caller='none', conn='38400',
> name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'

??

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* Better is the enemy of good enough. */