Setting up a Dial in server

Rvk <(E-Mail Removed)> wrote:

> some time later the PPD exits with a message PPPD died unexpectadly.

How long does the connection stay up before it goes down?

> Jun 2 18:33:10 cs pppd[21066]: Hangup (SIGHUP)
> Jun 2 18:33:10 cs pppd[21066]: Modem hangup

Ok, so for some reason, the connection gets disconnected from what would
appear to be the servers end.

What's in /etc/inittab on the server for this line?

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!

I am trying to set up a dial in server with RH9 on both server and
client. Although I can log in in the modem terminal I cannot continue
further. some time later the PPD exits with a message PPPD died
unexpectadly.

The messages on client is as follows:

Red Hat Linux release 9 (Shrike)
Kernel 2.4.20-8smp on an i686


abcd login: xxxxxxx
Password:
Last login: Tue Jun 1 18:31:15 on ttyS0
[xxxxxx@abcd xxxxx]$


The exit message on client is:

The pppd daemon died unexpectedly!
Exit status: 16

the pppd log on client is as follows:


Jun 2 18:32:43 cs pppd[21066]: pppd 2.4.1 started by root, uid 0
Jun 2 18:32:43 cs pppd[21066]: Using interface ppp0
Jun 2 18:32:43 cs pppd[21066]: Connect: ppp0 <--> /dev/ttyS0
Jun 2 18:33:10 cs pppd[21066]: Hangup (SIGHUP)
Jun 2 18:33:10 cs pppd[21066]: Modem hangup
Jun 2 18:33:10 cs pppd[21066]: Connection terminated.
Jun 2 18:33:10 cs pppd[21066]: Exit.


The message on the server in /var/log/mgetty.log.ttyS0 is :



06/02 18:16:50 yS0 mgetty: experimental test release 1.1.30-Dec16
06/02 18:16:50 yS0 check for lockfiles
06/02 18:16:50 yS0 locking the line
06/02 18:16:51 yS0 lowering DTR to reset Modem
06/02 18:16:51 yS0 send: \dATQ0V1H0[0d]
06/02 18:16:52 yS0 waiting for ``OK'' ** found **
06/02 18:16:52 yS0 send: ATS0=0Q0&D3&C1[0d]
06/02 18:16:52 yS0 waiting for ``OK'' ** found **
06/02 18:16:52 yS0 mdm_send: 'ATI'
06/02 18:16:52 yS0 Generic Rockwell modem (56000)
06/02 18:16:52 yS0 mdm_send: 'ATI3'
06/02 18:16:52 yS0 mdm_send: 'ATI4'
06/02 18:16:52 yS0 additional info: 'V.90 & K56Flex Voice Modem'
06/02 18:16:52 yS0 modem quirks: 0004
06/02 18:16:52 yS0 mdm_send: 'AT+FCLASS=2' -> OK
06/02 18:16:52 yS0 mdm_send: 'AT+FCLASS=0' -> OK
06/02 18:16:53 yS0 mdm_send: 'AT+FAA=1;+FCR=1' -> OK
06/02 18:16:53 yS0 mdm_send: 'AT+FBOR=0' -> OK
06/02 18:16:53 yS0 mdm_send: 'AT+FLID="49 115 xxxxxxxx"' -> OK
06/02 18:16:53 yS0 mdm_send: 'AT+FDCC=1,5,0,2,0,0,0,0' -> OK
06/02 18:16:53 yS0 waiting...
06/02 18:30:09 yS0 wfr: waiting for ``RING''
06/02 18:30:09 yS0 send: ATA[0d]
06/02 18:30:09 yS0 waiting for ``CONNECT'' ** found **
06/02 18:30:29 yS0 send:
06/02 18:30:29 yS0 waiting for ``_'' ** found **
06/02 18:30:36 ##### data dev=ttyS0, pid=13500, caller='none',
conn='38400', name='', cmd='/bin/login', user='xxxxxxx'


The message in /var/log/messages is:

un 2 18:30:36 abcd mgetty[13500]: data dev=ttyS0, pid=13500,
caller='none', conn='38400', name='', cmd='/bin/login', user='xxxxxx'
Jun 2 18:30:39 abcd login(pam_unix)[13500]: session opened for user
xxxxxx by LOGIN(uid=0)
Jun 2 18:30:39 abcd login -- xxxxx[13500]: DIALUP AT ttyS0 BY xxxxxx
Jun 2 18:30:39 abcd login -- xxxxxx[13500]: LOGIN ON ttyS0 BY xxxxxxx
Jun 2 18:32:00 abcd login(pam_unix)[13500]: session closed for user
xxxxxx

Can somebody advice how to set the connection up.

Regards
Raju

Rvk <(E-Mail Removed)> wrote:
> I am trying to set up a dial in server with RH9 on both server and
> client. Although I can log in in the modem terminal I cannot continue
> further. some time later the PPD exits with a message PPPD died
> unexpectadly.

> The messages on client is as follows:

> Red Hat Linux release 9 (Shrike)
> Kernel 2.4.20-8smp on an i686


> abcd login: xxxxxxx
> Password:
> Last login: Tue Jun 1 18:31:15 on ttyS0
> [xxxxxx@abcd xxxxx]$

It looks like you are using minicom to connect and then login. Doing
that won't work to create a PPP connection unless you start pppd on the
"server," either manually or with a special ppp account on the server.

There should be an "ISP" HOWTO somewhere at the RH web site that may be
worth reading.

--
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. */

(E-Mail Removed) (Rvk) wrote in message news:<(E-Mail Removed). com>...
> I am trying to set up a dial in server with RH9 on both server and
> client. Although I can log in in the modem terminal I cannot continue
> further. some time later the PPD exits with a message PPPD died
> unexpectadly.
>
....

> 06/02 18:30:09 yS0 waiting for ``CONNECT'' ** found **
> 06/02 18:30:29 yS0 send:
> 06/02 18:30:29 yS0 waiting for ``_'' ** found **
> 06/02 18:30:36 ##### data dev=ttyS0, pid=13500, caller='none',
> conn='38400', name='', cmd='/bin/login', user='xxxxxxx'
>

I don't see your pppd starting. Did you set it up right on the server?

>
> The message in /var/log/messages is:
>
> un 2 18:30:36 abcd mgetty[13500]: data dev=ttyS0, pid=13500,
> caller='none', conn='38400', name='', cmd='/bin/login', user='xxxxxx'
> Jun 2 18:30:39 abcd login(pam_unix)[13500]: session opened for user
> xxxxxx by LOGIN(uid=0)
> Jun 2 18:30:39 abcd login -- xxxxx[13500]: DIALUP AT ttyS0 BY xxxxxx
> Jun 2 18:30:39 abcd login -- xxxxxx[13500]: LOGIN ON ttyS0 BY xxxxxxx
> Jun 2 18:32:00 abcd login(pam_unix)[13500]: session closed for user
> xxxxxx
>
> Can somebody advice how to set the connection up.
>
> Regards
> Raju

your log says ... the pppd didn't start ... did you start that
manually? what did you use to connect? minicom or chat?

you can start pppd automatically from /etc/ininttab ....
like ... S2:2345:respawn:/sbin/mgetty ttyS2 -D /dev/ttyS2

start pppd in setuid mode ... chmod u+s /usr/sbin/pppd

add this line to env:

alias ppp="exec /usr/sbin/pppd -detach"

the common options for /etc/ppp/option.server

-detach
asyncmap 0
modem
crtscts
lock
proxyarp
ms-dns 12.34.45.78

hth

raqueeb hasssan
congo (drc)

Raqueeb Hassan <(E-Mail Removed)> wrote:
> your log says ... the pppd didn't start ... did you start that
> manually? what did you use to connect? minicom or chat?

Err.. No. The log shows that pppd started on the client and died
after the server side hung up, 21 seconds after login as shown by
the mgetty log. The reason for the hang up is not clear to me, but
apparently involves PAM - which I don't use.

> you can start pppd automatically from /etc/ininttab ....
> like ... S2:2345:respawn:/sbin/mgetty ttyS2 -D /dev/ttyS2

> start pppd in setuid mode ... chmod u+s /usr/sbin/pppd

> add this line to env:

> alias ppp="exec /usr/sbin/pppd -detach"

> the common options for /etc/ppp/option.server

> -detach
> asyncmap 0
> modem
> crtscts
> lock
> proxyarp
> ms-dns 12.34.45.78

And how is pppd started automatically?

A setup similar to the one you describe could work if "ppp" was
_manually_ entered at the command line after logging into the server
with minicom. It *might* also work automatically with a client pppd
chat script doing the login/password dance that sent "ppp" right
after login succeeds.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* My confidence in this answer (X), on a scale of 0 to 10:
|----|----|----|----|----|----|----|----|----|---X|
0----1----2----3----4----5----6----7----8----9----10 */

Cameron Kerr <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> Rvk <(E-Mail Removed)> wrote:
>
> > some time later the PPD exits with a message PPPD died unexpectadly.
>
> How long does the connection stay up before it goes down?
>
> > Jun 2 18:33:10 cs pppd[21066]: Hangup (SIGHUP)
> > Jun 2 18:33:10 cs pppd[21066]: Modem hangup
>
> Ok, so for some reason, the connection gets disconnected from what would
> appear to be the servers end.
>
> What's in /etc/inittab on the server for this line?

The line in /etc/inittab is:

s0:2345:respawn:/sbin/mgetty ttyS0 /dev/ttyS0

The PPPD ios supposed to be start auto matically. So the following is
added in /etc/mgetty+sendfax/login.config:

/AutoPPP/- -/usr/bin/pppd /etc/ppp/options.server

Contents of options.server is:

asyncmap 0
modem
crtscts
lock
login
require-pap
-chap
proxyarp
192.168.1.201:192.168.1.1


This is the standard on many posts I reffered to.
.. One point to note that the machines that I am used for testing is
already configured on a LAN with server address 192.168.1.201 and
client 192.168.1.1 ( I am new to this so I am using two conveniently
available machines. Is this any way affecting the dial up/in ? Both
server and client using RH9.

Can any body tell wahat is going wrong

Regards,

Raju

Clifford Kite <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> Rvk <(E-Mail Removed)> wrote:
> > I am trying to set up a dial in server with RH9 on both server and
> > client. Although I can log in in the modem terminal I cannot continue
> > further. some time later the PPD exits with a message PPPD died
> > unexpectadly.
>
> > The messages on client is as follows:
>
> > Red Hat Linux release 9 (Shrike)
> > Kernel 2.4.20-8smp on an i686
>
>
> > abcd login: xxxxxxx
> > Password:
> > Last login: Tue Jun 1 18:31:15 on ttyS0
> > [xxxxxx@abcd xxxxx]$
>
> It looks like you are using minicom to connect and then login. Doing
> that won't work to create a PPP connection unless you start pppd on the
> "server," either manually or with a special ppp account on the server.
>
> There should be an "ISP" HOWTO somewhere at the RH web site that may be
> worth reading.

Thanks for the reply: (I am splitting the didderent replies in to
different threads for clarity)

The PPPD is supposed to be start auto matically. So the following is
added in /etc/mgetty+sendfax/login.config:

/AutoPPP/- -/usr/bin/pppd /etc/ppp/options.server

Contents of options.server is:

asyncmap 0
modem
crtscts
lock
login
require-pap
-chap
proxyarp
192.168.1.201:192.168.1.1


This is the standard on many posts I reffered to.
.. One point to note that the machines that I am used for testing is
already configured on a LAN with server address 192.168.1.201 and
client 192.168.1.1 ( I am new to this so I am using two conveniently
available machines. Is this any way affecting the dial up/in ? Both
server and client using RH9.

Can any body tell wahat is going wrong.

Regards,

Raju

(E-Mail Removed) (Edward Lee epl) wrote in message news:<(E-Mail Removed) om>...
> (E-Mail Removed) (Rvk) wrote in message news:<(E-Mail Removed). com>...
> > I am trying to set up a dial in server with RH9 on both server and
> > client. Although I can log in in the modem terminal I cannot continue
> > further. some time later the PPD exits with a message PPPD died
> > unexpectadly.
> >
> ...
>
> > 06/02 18:30:09 yS0 waiting for ``CONNECT'' ** found **
> > 06/02 18:30:29 yS0 send:
> > 06/02 18:30:29 yS0 waiting for ``_'' ** found **
> > 06/02 18:30:36 ##### data dev=ttyS0, pid=13500, caller='none',
> > conn='38400', name='', cmd='/bin/login', user='xxxxxxx'
> >
>
> I don't see your pppd starting. Did you set it up right on the server?


The PPPD ios supposed to be start auto matically. So the following is
added in /etc/mgetty+sendfax/login.config:

/AutoPPP/- -/usr/bin/pppd /etc/ppp/options.server

Contents of options.server is:

asyncmap 0
modem
crtscts
lock
login
require-pap
-chap
proxyarp
192.168.1.201:192.168.1.1

The line in /etc/inittab is:

s0:2345:respawn:/sbin/mgetty ttyS0 /dev/ttyS0


This is the standard on many posts I reffered to.
.. One point to note that the machines that I am used for testing is
already configured on a LAN with server address 192.168.1.201 and
client 192.168.1.1 ( I am new to this so I am using two conveniently
available machines. Is this any way affecting the dial up/in ? Both
server and client using RH9.

Regards,

Raju
>
> >
> > The message in /var/log/messages is:
> >
> > un 2 18:30:36 abcd mgetty[13500]: data dev=ttyS0, pid=13500,
> > caller='none', conn='38400', name='', cmd='/bin/login', user='xxxxxx'
> > Jun 2 18:30:39 abcd login(pam_unix)[13500]: session opened for user
> > xxxxxx by LOGIN(uid=0)
> > Jun 2 18:30:39 abcd login -- xxxxx[13500]: DIALUP AT ttyS0 BY xxxxxx
> > Jun 2 18:30:39 abcd login -- xxxxxx[13500]: LOGIN ON ttyS0 BY xxxxxxx
> > Jun 2 18:32:00 abcd login(pam_unix)[13500]: session closed for user
> > xxxxxx
> >
> > Can somebody advice how to set the connection up.
> >
> > Regards
> > Raju

Clifford Kite <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> Raqueeb Hassan <(E-Mail Removed)> wrote:
> > your log says ... the pppd didn't start ... did you start that
> > manually? what did you use to connect? minicom or chat?
>
> Err.. No. The log shows that pppd started on the client and died
> after the server side hung up, 21 seconds after login as shown by
> the mgetty log. The reason for the hang up is not clear to me, but
> apparently involves PAM - which I don't use.
>
> > you can start pppd automatically from /etc/ininttab ....
> > like ... S2:2345:respawn:/sbin/mgetty ttyS2 -D /dev/ttyS2
>
> > start pppd in setuid mode ... chmod u+s /usr/sbin/pppd
>
> > add this line to env:
>
> > alias ppp="exec /usr/sbin/pppd -detach"
>
> > the common options for /etc/ppp/option.server
>
> > -detach
> > asyncmap 0
> > modem
> > crtscts
> > lock
> > proxyarp
> > ms-dns 12.34.45.78
>
> And how is pppd started automatically?
>
> A setup similar to the one you describe could work if "ppp" was
> _manually_ entered at the command line after logging into the server
> with minicom. It *might* also work automatically with a client pppd
> chat script doing the login/password dance that sent "ppp" right
> after login succeeds.


The options are already there.

The line in /etc/inittab is:
s0:2345:respawn:/sbin/mgetty ttyS0 /dev/ttyS0

In /etc/mgetty+sendfax/login.config
/AutoPPP/ - -/usr/bin/pppd /etc/ppp/options.server is included.

Contents of /etc/ppp/options.server
asyncmap 0
modem
crtscts
lock
login
require-pap
-chap
proxyarp
192.168.1.201:192.168.1.1

Regards,
Raju