From owner-freebsd-questions Wed May 3 22:10:20 2000 Delivered-To: freebsd-questions@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id F3F9337BF99 for ; Wed, 3 May 2000 22:10:14 -0700 (PDT) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.9.3) id BAA09878; Thu, 4 May 2000 01:03:23 -0400 (EDT) (envelope-from cjc) Date: Thu, 4 May 2000 01:03:23 -0400 From: "Crist J. Clark" To: Ryan Thompson Cc: Fabio Miranda , freebsd-questions@FreeBSD.ORG Subject: Re: Full report of network/server Message-ID: <20000504010323.C9561@cc942873-a.ewndsr1.nj.home.com> Reply-To: cjclark@home.com References: <20000503204015.15444.qmail@web111.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from ryan@sasknow.com on Wed, May 03, 2000 at 07:21:10PM -0600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 03, 2000 at 07:21:10PM -0600, Ryan Thompson wrote: > Fabio Miranda wrote to Ryan Thompson: [snip] > > 3. current network status: > > a. cat /etc/rc.lcoal: > > /hdlc/utils/hdlccfg /hdlc/utils/eth0.cfg eth0 > > /hdlc/utils/ifhdlc eth0 compress > > ifconfig eth0 inet 209.88.252.106 209.88.252.105 > > netmask 0xfffffff8 > > ifconfig eth0 alias 209.88.252.113 209.88.252.105 > > broadcast 0xfffffff8 > > route add default 209.88.252.105 > > route add -net 209.88.252.104/29 127.0.0.1 > > route add -net 209.88.252.112/29 127.0.0.1 I am not familiar with HDLC in FreeBSD, but I can say that those last two manually added routes look _very_ fishy. And below, > > b. ifconfig eth0 > > eth0: flags=51 mtu 1500 > > inet 209.88.252.106 --> 209.88.252.105 netmask > > 0xfffffff8 > > inet 209.88.252.113 --> 255.255.255.248 ^^^^^^^^^^^^^^^ > > netmask 0xffffff00 Is not correct. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message