From owner-freebsd-questions Sun May 14 1:42:30 2000 Delivered-To: freebsd-questions@freebsd.org Received: from usc.edu (usc.edu [128.125.253.136]) by hub.freebsd.org (Postfix) with ESMTP id 82B9A37B873 for ; Sun, 14 May 2000 01:42:26 -0700 (PDT) (envelope-from abdulgha@usc.edu) Received: from scf-fs.usc.edu (root@scf-fs.usc.edu [128.125.253.183]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id BAA11847 for ; Sun, 14 May 2000 01:42:26 -0700 (PDT) Received: from phoenix (res-3617.usc.edu [128.125.31.111]) by scf-fs.usc.edu (8.9.3.1/8.9.3/usc) with SMTP id BAA20220 for ; Sun, 14 May 2000 01:42:26 -0700 (PDT) Message-ID: <002d01bfbd80$600272e0$6f1f7d80@phoenix> Reply-To: "Khairuddin Abdul Ghani" From: "Khairuddin Abdul Ghani" To: References: <024901bfbd1a$0bc12570$6f1f7d80@phoenix> <391E3DC8.6947DBCD@gorean.org> Subject: named errors (was Re: assigning two C IP blocks to one machine) Date: Sun, 14 May 2000 01:42:44 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, again! Thanks for all the help, esp. to Crist and Doug. it seems that my settings were correct after all, just that those people on the other side didn't actually do what they were supposed to with the IP's. Anyhow, there are other things I'm concerned about, which are the error messages that named produces while loading, something about not being able to open enough files. Here're the log entries: -- snip snip -- May 14 01:35:54 sage named[36092]: starting. named 8.2.2-P5-NOESW Sun May 14 01:17:55 PDT 2000 May 14 01:35:54 sage named[36092]: limit files set to fdlimit (1024) May 14 01:35:55 sage named[36092]: fcntl(dfd, F_DUPFD, 20): Too many open files May 14 01:35:55 sage named[36092]: fcntl(sfd, F_DUPFD, 20): Too many open files May 14 01:35:55 sage named[36092]: fcntl(dfd, F_DUPFD, 20): Too many open files May 14 01:35:55 sage named[36092]: fcntl(sfd, F_DUPFD, 20): Too many open files May 14 01:35:55 sage named[36092]: fcntl(dfd, F_DUPFD, 20): Too many open files May 14 01:35:55 sage named[36092]: fcntl(sfd, F_DUPFD, 20): Too many open files May 14 01:35:55 sage named[36092]: fcntl(dfd, F_DUPFD, 20): Too many open files May 14 01:35:55 sage named[36092]: fcntl(sfd, F_DUPFD, 20): Too many open files May 14 01:35:55 sage named[36092]: fcntl(dfd, F_DUPFD, 20): Too many open files May 14 01:35:55 sage named[36092]: fcntl(sfd, F_DUPFD, 20): Too many open files May 14 01:35:55 sage named[36092]: fcntl(dfd, F_DUPFD, 20): Too many open files May 14 01:35:55 sage named[36092]: fcntl(sfd, F_DUPFD, 20): Too many open files May 14 01:35:55 sage named[36092]: fcntl(dfd, F_DUPFD, 20): Too many open files May 14 01:35:55 sage named[36092]: fcntl(sfd, F_DUPFD, 20): Too many open files May 14 01:35:55 sage named[36092]: socket(SOCK_DGRAM): Too many open files May 14 01:35:55 sage named[36092]: deleting interface [127.0.0.1].53 May 14 01:35:55 sage named[36093]: couldn't create pid file '/var/run/named.pid' May 14 01:35:55 sage named[36093]: Ready to answer queries. -- snip snip -- Later on, when i send named a HUP signal, it dies with the message: can't open '/etc/namedb/named.conf' I have about 26 different SOA files that named needs to look up, and I'm not sure what change to the kernel started causing this. Doesn't seem like a limit problem with login.conf either. Currently using 4.0-RELEASE btw. Thanks again to all. :) - Khairuddin ----- Original Message ----- From: "Doug Barton" To: "Khairuddin Abdul Ghani" Cc: Sent: Saturday, May 13, 2000 10:46 PM Subject: Re: assigning two C IP blocks to one machine Khairuddin Abdul Ghani wrote: > > Hello. I currently have two blocks of IPs to be used on a single machine, > but I can't seem to get the new block working. > > I have old IPs a.a.a.2 assigned and a.a.a.3-a.a.a.254 aliased with a.a.a.1 > as "defaultrouter" and broadcast IP of a.a.a.255. > > I added aliases for the new block b.b.b.2-b.b.b.254, but they don't work. This is far from my area of expertise, but my understanding is that for new network blocks you need to add the first address as a regular address (b.b.b.2 netmask 255.255.255.0) without the alias. Then add the remaining addresses in that block as aliases to it (b.b.b.3 netmask 255.255.255.255 alias). The definition of "new network block" will be dependent on how the first block is defined. > Am I missing something, some setting in rc.conf perhaps? Thanks, as this is > my first post, I hope it's technical enough to be here. Not to worry. This list is for all questions related to FreeBSD. The only time you will run into problems is if you ask a question that is covered by the handbook or in the mail archives. Get in the habit of checking them first. Good luck, Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message