Do not see the password prompt when dialing into a modem

Hello,

I have a USB to DB9 serial converter attached to a USB port. And it
is connected to a modem thru a DB9 to DB25 converter. mgetty is
attached to the /dev/ttyUSB0 port. I can dial into the modem and get
the login prompt but not the password prompt. Is it because the baud
rates are set incorrect? Any clue on this will be appreciated.

Thanks,
Shanthi.

(E-Mail Removed) (Shanthi Paladugu) wrote:
>Hello,
>
> I have a USB to DB9 serial converter attached to a USB port. And it
>is connected to a modem thru a DB9 to DB25 converter. mgetty is
>attached to the /dev/ttyUSB0 port. I can dial into the modem and get
>the login prompt but not the password prompt. Is it because the baud
>rates are set incorrect? Any clue on this will be appreciated.

That appears to be an mgetty configuration problem. I'm going
on memory here, and may get the exact details wrong... so you
want to read the man pages and go through mgetty's configuration
with care. Also see the configuration for the login program, as
it could be that too.

The hint is that you see the username prompt, and never get to
the password prompt. If my memory is right, mgetty provides the
username prompt, and then hands off the username to login, which
queries for a password. If it fails to match, the next prompt
for a username comes, not from mgetty, but from login.

--
Floyd L. Davidson <http://web.newsguy.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) (E-Mail Removed)

(E-Mail Removed) (Floyd L. Davidson) wrote in message news:<(E-Mail Removed)>...
> (E-Mail Removed) (Shanthi Paladugu) wrote:
> >Hello,
> >
> > I have a USB to DB9 serial converter attached to a USB port. And it
> >is connected to a modem thru a DB9 to DB25 converter. mgetty is
> >attached to the /dev/ttyUSB0 port. I can dial into the modem and get
> >the login prompt but not the password prompt. Is it because the baud
> >rates are set incorrect? Any clue on this will be appreciated.
>
> That appears to be an mgetty configuration problem. I'm going
> on memory here, and may get the exact details wrong... so you
> want to read the man pages and go through mgetty's configuration
> with care. Also see the configuration for the login program, as
> it could be that too.
>
> The hint is that you see the username prompt, and never get to
> the password prompt. If my memory is right, mgetty provides the
> username prompt, and then hands off the username to login, which
> queries for a password. If it fails to match, the next prompt
> for a username comes, not from mgetty, but from login.



But the same mgetty config works with a USB cable and a USB modem directly.

Shanthi Paladugu <(E-Mail Removed)> wrote:
> (E-Mail Removed) (Floyd L. Davidson) wrote in message news:<(E-Mail Removed)>...
>> (E-Mail Removed) (Shanthi Paladugu) wrote:
>> >Hello,
>> >
>> > I have a USB to DB9 serial converter attached to a USB port. And it
>> >is connected to a modem thru a DB9 to DB25 converter. mgetty is
>> >attached to the /dev/ttyUSB0 port. I can dial into the modem and get
>> >the login prompt but not the password prompt. Is it because the baud
>> >rates are set incorrect? Any clue on this will be appreciated.
>>
>> That appears to be an mgetty configuration problem. I'm going
>> on memory here, and may get the exact details wrong... so you
>> want to read the man pages and go through mgetty's configuration
>> with care. Also see the configuration for the login program, as
>> it could be that too.
>>
>> The hint is that you see the username prompt, and never get to
>> the password prompt. If my memory is right, mgetty provides the
>> username prompt, and then hands off the username to login, which
>> queries for a password. If it fails to match, the next prompt
>> for a username comes, not from mgetty, but from login.

> But the same mgetty config works with a USB cable and a USB modem
> directly.

The "same mgetty config" probably won't work with a "USB/DB9/DB25
converter." I've never used such a setup but I'd expect the device
file to which mgetty must attach to be a ttySx, not ttyUSB0.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* I gave up on politics when no matter who I voted for, I regretted it.
* -- Pepper...and Salt, WSJ */

In article <(E-Mail Removed) >
(E-Mail Removed) (Shanthi Paladugu) writes:

>(E-Mail Removed) (Floyd L. Davidson) wrote in message
>news:<(E-Mail Removed)>...
>
>> (E-Mail Removed) (Shanthi Paladugu) wrote:
>
>>>Hello,
>>>
>>> I have a USB to DB9 serial converter attached to a USB port. And
>>>it is connected to a modem thru a DB9 to DB25 converter. mgetty is
>>>attached to the /dev/ttyUSB0 port. I can dial into the modem and get
>>>the login prompt but not the password prompt. Is it because the baud
>>>rates are set incorrect? Any clue on this will be appreciated.
>>
>> That appears to be an mgetty configuration problem. I'm going
>> on memory here, and may get the exact details wrong... so you
>> want to read the man pages and go through mgetty's configuration
>> with care. Also see the configuration for the login program, as
>> it could be that too.
>>
>> The hint is that you see the username prompt, and never get to
>> the password prompt. If my memory is right, mgetty provides the
>> username prompt, and then hands off the username to login, which
>> queries for a password. If it fails to match, the next prompt
>> for a username comes, not from mgetty, but from login.
>
>But the same mgetty config works with a USB cable and a USB modem
>directly.

Could it be a buffering issue? Many buffered text I/O routines
automatically flush the buffer on a newline - but since the
password prompt isn't followed by a newline, perhaps it's still
sitting in a buffer somewhere, with no fflush() to force it out.

Have you tried typing your password anyway? Maybe it'll still
work...

--
/~\ (E-Mail Removed)lid (Charlie Gibbs)
\ / I'm really at ac.dekanfrus if you read it the right way.
X Top-posted messages will probably be ignored. See RFC1855.
/ \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!

Charlie Gibbs <(E-Mail Removed)> scribbled:
> --
> /~\ (E-Mail Removed)lid (Charlie Gibbs)
> \ / I'm really at ac.dekanfrus if you read it the right way.
> X Top-posted messages will probably be ignored. See RFC1855.
> / \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!
>

Bad sig delimeters (no space after the --) which force people to see your
sig will get your posts ignored too. As will sigs with too many lines, blank
or no.

Can you say "hypocrite", boys and girls?

Shall we killfile this jerk? I'll go first.

--
There's no place like $HOME

> mgetty is attached to the /dev/ttyUSB0 port.

sorry to be awkward ... I don't get this .... how can that be
possible? ttyUSB0? can someone please explain?

raqueeb hassan
congo (drc)

In article <%xovc.20727$(E-Mail Removed). net>
(E-Mail Removed) (Larry Townsend) writes:

>Charlie Gibbs <(E-Mail Removed)> scribbled:
>> --
>> /~\ (E-Mail Removed)lid (Charlie Gibbs)
>> \ / I'm really at ac.dekanfrus if you read it the right way.
>> X Top-posted messages will probably be ignored. See RFC1855.
>> / \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!
>>
>
>Bad sig delimeters (no space after the --) which force people to see
>your sig will get your posts ignored too.

OK, so there was a slip-up on my end. Normally the space is there.
I suppose you're now going to dump all over Floyd, whose .sig got
out without the trailing space too.

>As will sigs with too many lines, blank or no.

Four lines. Count 'em. Standard stuff.

>Can you say "hypocrite", boys and girls?

Jeez, who pissed in your corn flakes this morning?

>Shall we killfile this jerk? I'll go first.

I will if you will...

--
/~\ (E-Mail Removed)lid (Charlie Gibbs)
\ / I'm really at ac.dekanfrus if you read it the right way.
X Top-posted messages will probably be ignored. See RFC1855.
/ \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!

On 3 Jun 2004 08:38:44 -0700, (E-Mail Removed) (Raqueeb Hassan)
wrote:

>> mgetty is attached to the /dev/ttyUSB0 port.
>
>sorry to be awkward ... I don't get this .... how can that be
>possible? ttyUSB0? can someone please explain?
>
>raqueeb hassan
>congo (drc)

What don't you get? The modem is plugged into a USB port.

Mike-

--
If you're not confused, you're not trying hard enough.
--
Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If
email from you bounces, try non-HTML, non-encoded, non-attachments,


----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---

"Charlie Gibbs" <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> In article <(E-Mail Removed) >
> (E-Mail Removed) (Shanthi Paladugu) writes:
>
> >(E-Mail Removed) (Floyd L. Davidson) wrote in message
> >news:<(E-Mail Removed)>...
> >
> >> (E-Mail Removed) (Shanthi Paladugu) wrote:
>
> >>>Hello,
> >>>
> >>> I have a USB to DB9 serial converter attached to a USB port. And
> >>>it is connected to a modem thru a DB9 to DB25 converter. mgetty is
> >>>attached to the /dev/ttyUSB0 port. I can dial into the modem and get
> >>>the login prompt but not the password prompt. Is it because the baud
> >>>rates are set incorrect? Any clue on this will be appreciated.
> >>
> >> That appears to be an mgetty configuration problem. I'm going
> >> on memory here, and may get the exact details wrong... so you
> >> want to read the man pages and go through mgetty's configuration
> >> with care. Also see the configuration for the login program, as
> >> it could be that too.
> >>
> >> The hint is that you see the username prompt, and never get to
> >> the password prompt. If my memory is right, mgetty provides the
> >> username prompt, and then hands off the username to login, which
> >> queries for a password. If it fails to match, the next prompt
> >> for a username comes, not from mgetty, but from login.
> >
> >But the same mgetty config works with a USB cable and a USB modem
> >directly.
>
> Could it be a buffering issue? Many buffered text I/O routines
> automatically flush the buffer on a newline - but since the
> password prompt isn't followed by a newline, perhaps it's still
> sitting in a buffer somewhere, with no fflush() to force it out.
>
> Have you tried typing your password anyway? Maybe it'll still
> work...

I did try typing the password thought I do not see the prompt. It did
not work. The windows dialup client exits with the message "The
scripts has halted".