From owner-freebsd-isp Tue Jun 25 20:14:35 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA29089 for isp-outgoing; Tue, 25 Jun 1996 20:14:35 -0700 (PDT) Received: from mail.transport.com (root@transport.com [204.119.17.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA29083 for ; Tue, 25 Jun 1996 20:14:32 -0700 (PDT) Received: from connect.transport.com (pdx43.transport.com [204.119.17.43]) by mail.transport.com (8.7.3/8.6.10) with SMTP id UAA12781 for ; Tue, 25 Jun 1996 20:14:29 -0700 Date: Tue, 25 Jun 1996 20:14:29 -0700 Message-Id: <199606260314.UAA12781@mail.transport.com> X-Sender: connect@mail.transport.com X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-isp@freebsd.org From: Pete Chiboucas Subject: Certain IP's vanish- HELP! Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We have a couple of FreeBSD boxes running Apache and being Virtual Domain Servers. One family of IP addresses works fine and another randomly chooses to become unavailable. The family that always works is part of the family spec'ed in sysconfig as the network interface. The same family is also spec'ed as "your-net" in /etc/networks. Both of above references specify a netmask of 255.255.255. For some reason virtuals that are assigned IP addresses outside of the spec'ed family will just stop working. Help if you can this is driving a bunch of people nuts. Thanks Pete ****************************************************** Strength is Gentle, Wisdom Quiet, Passion Overwhelming Net Connection/Pete Chiboucas www.webnw.com 8888 SW Cashmur Ln pete@webnw.com Portland Or 97225 503 203 1671