From owner-freebsd-isp Sat Mar 11 12:34:43 2000 Delivered-To: freebsd-isp@freebsd.org Received: from awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id EBDAC37B84A; Sat, 11 Mar 2000 12:32:25 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA18142; Sat, 11 Mar 2000 20:31:23 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA12980; Sat, 11 Mar 2000 20:31:10 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200003112031.UAA12980@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brian Somers , Nik Clayton , Lee Johnston , freebsd-users@uk.freebsd.org, brian@hak.lan.Awfulhak.org, freebsd-isp@FreeBSD.org Subject: Re: ispsetup (was: Re: FreeBSD in Dixons) In-Reply-To: Message from dom@happygiraffe.net (Dominic Mitchell) of "Sat, 11 Mar 2000 18:11:52 GMT." <20000311181152.A1206@myrddin.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Mar 2000 20:31:10 +0000 From: Brian Somers Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I haven't looked at the code yet, but.... > Comments: > * It *really* needs a better interface. I think dialog would be good > and would match tzsetup(8). > * It really shows why you should do stuff like this in perl or python. > Some of sh's programming constructs are very obscure and > unmaintanable... probably true. > * We need to sit down together and figure out 90% of the variables > needed to configure each service for an isp. There are a number of > issues involved. The biggie for me is how to do resolv.conf > correctly, even in the case of multiple isp's (not all of them give > DNS configuration through IPCP). This has just got better. There's now (patch ready for Monday) a ``resolv'' command in ppp: resolv command This command controls ppps manipulation of the resolv.conf(5) file. When ppp starts up, it loads the contents of this file into memory and retains this image for future use. command is one of the follow- ing: readonly Treat /etc/resolv.conf as read only. If ``dns'' is en- abled, ppp will still attempt to negotiate nameservers with the peer, making the results available via the DNS0 and DNS1 macros. This is the opposite of the ``resolv writable'' command. reload Reload /etc/resolv.conf into memory. This may be necessary if for example a DHCP client overwrote /etc/resolv.conf. restore Replace /etc/resolv.conf with the version originally read at startup or with the last ``resolv reload'' command. This is sometimes a useful command to put in the /etc/ppp/ppp.linkdown file. rewrite Rewrite the /etc/resolv.conf file. This command will work even if the ``resolv readonly'' command has been used. It may be useful as a command in the /etc/ppp/ppp.linkup file if you wish to defer updating /etc/resolv.conf until after other commands have finished. writable Allow ppp to update /etc/resolv.conf if ``dns'' is enabled and ppp successfully negotiates a DNS. This is the oppo- site of the ``resolv readonly'' command. Most ISPs (are Demon the only ones that don't these days?) will negotiate DNS during IPCP. If they don't, we need to put them in the config file. We always want ``resolv restore'' in ppp.linkdown. Ppp is then happy to rewrite resolv.conf and put it back when it's done, but for those of us who use named, we want a small ``setdns'' script. I happen to have a rather crude one here that replaces the forwarders line in named.conf and HUPs named. I could tart it up a bit and the use of it could be based on /etc/rc.conf containing named_enable=YES. > * A number of configuration issues depend on which port/package has been > installed. eg: sendmail vs postifx vs exim vs qmail or perhaps squid > vs. wwwoffle. I'm not entirely sure how best to approach this. I reckon the aim should be to provide a list of possibilities, indicating which of these would need to be installed. The possibilities would be limited to what the writer understands/knows/ likes... > Anyway, have a look and let me know what you think. > > -Dom Will do. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message