Quoting acop ([EMAIL PROTECTED]): [much snipped] > Jan 27 15:47:17 HQ pppd[209]: local IP address 134.99.138.64 > Jan 27 15:47:17 HQ pppd[209]: remote IP address 195.158.131.195 > Jan 27 15:48:19 HQ pppd[209]: Hangup (SIGHUP) > Jan 27 15:48:19 HQ pppd[209]: Modem hangup > Jan 27 15:48:19 HQ pppd[209]: Connection terminated. > Jan 27 15:48:19 HQ pppd[209]: Exit. > > --my 'options' : > > connect '/usr/sbin/chat -v -f /etc/ppp/ppp.chat' > /dev/modem > 115200 > defaultroute > noipdefault > debug > crtscts > lock > modem > user ######### > > --my 'ppp.up' : (to start the connection) > > localip=0.0.0.0 > remoteip= > device=/dev/modem > pppflags="115200 modem debug defaultroute" > /usr/sbin/pppd lock connect \ > '/usr/sbin/chat -v -f /etc/ppp/ppp.chat' \ > $device $pppflags $localip:$remoteip > > The Problem is that the first established connection is o.k. but when I > kill the > pppd and try to establish another one it stops after some seconds with > the > messages as shown above.
Interesting that the link stays up for exactly a minute. On the face of it, I can only see one mistake, which is to use /dev/modem. I reckon you've got something else running, mgetty say, that also wants to use the modem. If one process is locking /dev/modem, and another is locking /dev/ttyS1, say, then you're screwed. Best remove /dev/modem from your system and use the real name throughout. I hope this has the required effect. Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
