From owner-freebsd-current Wed Nov 19 17:32:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA22788 for current-outgoing; Wed, 19 Nov 1997 17:32:55 -0800 (PST) (envelope-from owner-freebsd-current) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA22768 for ; Wed, 19 Nov 1997 17:32:47 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id AAA12234; Thu, 20 Nov 1997 00:16:44 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199711200016.AAA12234@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: jcondon cc: "freebsd-current@FreeBSD.ORG" Subject: Re: ppp pmdemand dials when I dont want it to In-reply-to: Your message of "Wed, 19 Nov 1997 13:33:48 EST." <3473310C.EEF454E2@computer.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Nov 1997 00:16:43 +0000 From: Brian Somers Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Been wrestling with this for about a week. Started running 2.2.2 and > did a fresh reinstall to 2.2.5. All seems to work fine except it dials > and apperently does DNS lookups for apperently no reason. I have > removed the -q option on Sendmail, and disabled Sendmail altogether. > When I unplug the ethernet cable from the Win95 machine, or dialup via > its own modem / DUN it doesn't cause the UNIX box to dial in. However > when the Win95 is plugged into the ethernet and running nothing more > then explorer and systay it will dial in with in 15 mins usually > sooner. I did notice that if I dial in with the Win95 box and do > NOTHING it sends about 250 bytes a min and receives about 15K. Could > this have something to do with it? [.....] I think you really need to find out what's being looked up in each case and stop each lookup at source, *or*........ I've never really used demand dialing, it simply never does what you want it to do. I sat down and thought about it at one point, and decided that I've basically got a network that I use personally. I don't want arbitrary DNS lookups to trigger a dialup, and I don't want sendmail doing a dialup as soon as I press "Send" on my mailer - I've normally got more than one thing to send. I don't want the machine to dialup while I'm not there *except* to do a cvsup and exchange news & mail at some early hour of the morning. In fact, the only time I actually want to ``demand dial'' is when I'm actually sitting in front of the machine and think "I want a connection". These thoughts triggered the fixing of -background mode and the birth of pppctl. The pppctl man page essentially has examples of the scripts I use (available from all machines on my network) to make a connection. I run ppp in -auto mode so that there's never any contention trying to start two at once. I have six FvwmButtons on my desktop - "Connect 30", "Connect 60", "Connect 120", "Connect 300", "Disconnect" and "Hangup". The "Hangup" script sends a HUP to ppp, and the rest are invocations of the stuff in pppctl(8). Even under M$, I have buttons that connect a telnet session to one of the FreeBSD boxes on a specific port. Inetd runs a script that does the "connect 300" or whatever. The script exits and the M$ box loses the connection. Of course I had to install some third party freeware telnet implemenation 'cos the M$ one starts stuffing dialogue boxes in your face when the connection drops :-| So, every machine I sit in front of (or switch to) has a set of connect/disconnect buttons or scripts, and ppp doesn't do *any* unwanted dialing ! Perhaps I ought to ramble on about this in the FAQ :-) > Thanks for any insight you could provide. > > Jim Condon -- Brian , , Don't _EVER_ lose your sense of humour....