dialling out with vgetty

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Edmund GRIMLEY EVANS wrote:
> =

> I asked:
> =

> > Has anyone had any success with getting vgetty to dial out?
> =

> Thanks to the people who replied.
> =

> It's working now.

I=B4m really sorry, I think I missed this discussion. And maybe I have a
similar problem as well.

Has anyone had any success with using "diald" and "vgetty" on the same
device (e.g. ttyS*)?? Well, generally it is working, but there are one
thing, that isn't quite working:

If there is a request for the "outer-network", so diald is responding to
this and tries to dialout, it will begin to do it, will lock the device,
vgetty really frees it, but the connect script dies anyway.

Sometimes, it will not die and the diald is able to connect. After
closing down the idle link, vgetty will come "back-to-life" (it never
died though) and everything is fine.
But I have no idea why the diald is just working sometimes.
It does not seem to follow any "rule", if it'll work and if it will die.

I tried to use the cua* device for diald to call out, I tried vgetty to
lock the device, I tried various other configurations but the only
configuration which is good enough to work the way I described above is
this:

in the inittab

	#
	# in runlevel 3 vgetty with own issue on device ttyS1
	# =

	mo:3:respawn:/usr/sbin/vgetty -i /etc/issue.modem ttyS1
	#

the diald is started with following options in runlevel 3


  	/usr/sbin/diald -file $DIALDDIR/$PROVIDER.diald \
      	connect "/usr/sbin/chat -f $PPPDIR/$PROVIDER.chat" \
      	pidfile "diald$I.pid" \              =

     	-- file $PPPDIR/$PROVIDER.options


where $PROVIDER.diald contains

	device /dev/ttyS1
	modem
	lock
	-m ppp
	speed 115200
	two-way
	local 127.0.0.3
	remote 127.0.0.2
	reroute
	defaultroute
	dynamic
	disconnect-timeout 120
	redial-timeout 30
	dial-fail-limit 5
	nodev-retry-timeout 15
	fifo /var/run/diald.ctl

and $PROVIDER.chat

	TIMEOUT 30
	ABORT "NO CARRIER"
	ABORT BUSY
	ABORT "NO DIALTONE"
	ABORT ERROR
	"" +++ATZ0
	OK ATDTxxxPHONE-NUMBERxxx
	CONNECT

and $PROVIDER.options

	noipdefault
	ipcp-accept-local
	ipcp-accept-remote
	noipdefault
	-vjccomp
	-ac
	-pc
	-bsdcomp

allthough the $PROVIDER.options isn't causing the problem, after the
connect-script was successful, the pppd starts without problems.

So, the only thing I can't solve is, why does the diald not success in
dialing out sometimes and why is the diald successful sometimes. BTW,
I'm pretty sure, that it is not a problem with connecting to the
provider, because the modem does not start to dial! So I think the
problem is, that the connect script (chat) is not able to initialize the
modem! But, well, sometimes it is able to do it...

Is there anybody out there, who solved this kind of problem?

Thanx for answering,

Christian

PS:
These are some messages, that may be useful:

/var/log/vgetty.ttyS1
06/30 21:10:51 yS1  Rockwell detected
06/30 21:10:51 yS1  initializing ROCKWELL voice modem
06/30 21:10:52 yS1  waiting...

then diald requests the device (tries to dialout):

/var/log/vgetty.ttyS1
06/30 21:11:07 yS1  lock not made: lock file exists (pid=3D4673)

in /var/log/messages
Jun 30 21:11:07 papa diald[4673]: Running connect (pid =3D 4821).
Jun 30 21:11:09 papa chat[4821]: Failed =

Jun 30 21:11:09 papa diald[4673]: Connect script failed.
Jun 30 21:11:10 papa diald[4673]: Delaying 30 seconds before clear to
dial.

and afterwards in =

/var/log/vgetty.ttyS1
06/30 21:11:23 yS1  vgetty: experimental test release 0.9.0 / 09Sep98
06/30 21:11:23 yS1  mgetty: experimental test release 1.1.18-Sep11
06/30 21:11:23 yS1  reading generic configuration from config file
/etc/mgetty+s
endfax/voice.conf
06/30 21:11:23 yS1  reading program vgetty configuration from config
file /etc/m
getty+sendfax/voice.conf
06/30 21:11:23 yS1  reading port ttyS1 configuration from config file
/etc/mgett
y+sendfax/voice.conf
06/30 21:11:23 yS1  check for lockfiles
06/30 21:11:23 yS1  locking the line
06/30 21:11:23 yS1  lowering DTR to reset Modem
06/30 21:11:25 yS1  detecting voice modem type
(...)
06/30 21:11:26 yS1  Rockwell detected
06/30 21:11:26 yS1  initializing ROCKWELL voice modem
06/30 21:11:27 yS1  waiting...

vgetty is back on line...

--
As far as you can, enjoy every moment of every day.
---ICQ#21196326---mailto:ch.wagner@gmx.net---