From owner-freebsd-newbies Sun Sep 23 14:18:58 2001 Delivered-To: freebsd-newbies@freebsd.org Received: from msg-proxy4.mweb.co.za (msg-proxy4.mweb.co.za [196.2.46.16]) by hub.freebsd.org (Postfix) with ESMTP id 063C137B403 for ; Sun, 23 Sep 2001 14:18:52 -0700 (PDT) Received: from siberiyan.dyndns.org ([196.30.181.236]) by msg-proxy4.mweb.co.za (iPlanet Messaging Server 5.1 (built May 7 2001)) with SMTP id <0GK4006J1WJAH8@msg-proxy4.mweb.co.za> for freebsd-newbies@FreeBSD.ORG; Sun, 23 Sep 2001 23:18:49 +0200 (SAST) Received: by siberiyan.dyndns.org (sSMTP sendmail emulation); Sun, 23 Sep 2001 23:19:11 +0200 Date: Sun, 23 Sep 2001 23:19:11 +0200 From: Piet Delport Subject: Re: PPP what next! In-reply-to: <20010923145634.S49297-100000@lucifer.fuzion.ath.cx> To: The Psychotic Viper Cc: Dru , Raymond Pert , freebsd-newbies@FreeBSD.ORG Mail-Followup-To: The Psychotic Viper , Dru , Raymond Pert , freebsd-newbies@FreeBSD.ORG Message-id: <20010923231911.B1327@athalon> MIME-version: 1.0 Content-type: multipart/signed; boundary=tjCHc7DPkfUGtrlw; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline User-Agent: Mutt/1.3.22.1i X-Operating-System: FreeBSD 4.4-STABLE X-Editor: VIM - Vi IMproved 6.0ax BETA (http://www.vim.org/) X-Crypto: gpg (GnuPG) 1.0.6 (http://www.gnupg.org/) X-GPG-Key-ID: 0x6B191427 X-GPG-Fingerprint: C7FF A540 2199 F7BF 1933 5640 CD15 0FF3 6B19 1427 References: <20010923025411.A23038@athalon> <20010923145634.S49297-100000@lucifer.fuzion.ath.cx> Sender: owner-freebsd-newbies@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --tjCHc7DPkfUGtrlw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, 23 Sep 2001 at 15:01:43 +0200, The Psychotic Viper wrote: > On Sun, 23 Sep 2001, Piet Delport wrote: > > On Wed, 19 Sep 2001 at 07:32:15 -0400, Dru wrote: > > > If your prompt changes to all caps or PPP, you're connected. > > > You've also lost that prompt for the duration of your connection, > > > so open up another terminal using your ALT Function keys. Running > > > a trace route or a ping to a URL is a good connection test. When > > > you're finished, return to the terminal with the PPP prompt and > > > type the word by. > > > > The prompt isn't necessarily lost. You can press to > > suspend PPP and return to your prompt, then immediately type `bg' to > > let it continue executing in the background. > > > > To shut it down again, type `fg' to bring it into the foreground, > > then `close' to close the connection. >=20 > Just a note though, when u fork ppp AFAIK it stops data transfer for > the period you suspend it. You could try the 'bg' command inside > ppp(IIRC does the same as forking though) , or 'shell'. I personally > start ppp with the -background option and recall ppp if i need it then > 'quit' it to return to the prompt(does not kill my ppp). Killing ppp > is simply done with a killall -INT ppp. Works fine for me and I have a > working ppp and the full use of all my local ttys. Yep, that's the better way. :-) Personally, i use a socket to control ppp. My ppp.conf contains a line like this: set socket /var/run/ppp "" 0117 Then, i have a script called `pppdial' that contains something like: #!/bin/sh /usr/sbin/ppp -background && /usr/local/sbin/ipcheck and a script called `pppc' that contains: #!/bin/sh exec /usr/sbin/pppctl /var/run/ppp "$@" Now, i go `pppdial' to connect, `pppc close' to disconnect, `pppc show ipcp' to show statistics, and so on. A plain `pppc' gets me an interactive session. --=20 Piet Delport Today's subliminal thought is: --tjCHc7DPkfUGtrlw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) iD8DBQE7rlHPzRUP82sZFCcRAuxAAKCY23jws6UANO+LcrApEQ20DHenkwCfZ6vd UPanDdtL20y3uSYecz3SVX4= =JsTY -----END PGP SIGNATURE----- --tjCHc7DPkfUGtrlw-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-newbies" in the body of the message