From owner-freebsd-net@FreeBSD.ORG Wed Mar 16 10:02:27 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 645D616A4CE for ; Wed, 16 Mar 2005 10:02:27 +0000 (GMT) Received: from ints.mail.pike.ru (ints.mail.pike.ru [195.9.45.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id C244843D49 for ; Wed, 16 Mar 2005 10:02:25 +0000 (GMT) (envelope-from babolo@cicuta.babolo.ru) Received: (qmail 60709 invoked from network); 16 Mar 2005 10:02:24 -0000 Received: from cicuta.babolo.ru (194.135.49.133) by ints.mail.pike.ru with SMTP; 16 Mar 2005 10:02:24 -0000 Received: (nullmailer pid 2804 invoked by uid 136); Wed, 16 Mar 2005 10:02:41 -0000 X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: <20050315135749.A92893@ganymede.hub.org> To: "Marc G. Fournier" Date: Wed, 16 Mar 2005 13:02:41 +0300 (MSK) From: "."@babolo.ru X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <1110967361.940194.2803.nullmailer@cicuta.babolo.ru> cc: dima <_pppp@mail.ru> cc: "."@babolo.ru cc: net@freebsd.org Subject: Re: Re[2]: High ping latency using two ethernet under FreeBSD 4.11 ... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Mar 2005 10:02:27 -0000 > On Tue, 15 Mar 2005 .@babolo.ru wrote: > > >> but didn't think this was doable ... > > Why not: > > ifconfig fxp0 inet 200.46.204.2/24 > > ifconfig fxp0 inet 200.46.208.2/24 alias > > ifconfig fxp0 inet 200.46.204.10/32 alias > > ifconfig fxp0 inet 200.46.204.5/32 alias > > ifconfig fxp0 inet 200.46.208.254/32 alias > > ifconfig fxp0 inet 200.46.208.251/32 alias > > ifconfig fxp0 inet 200.46.208.244/32 alias > > so on > > ? > > With the only fxp0 interface > Great ... I have a new server going down next week that I'll try out the > ng_fec stuff with, and the above, then ... thanks ... If addresses and not bandwidth is reason, no need for ng_fec. > > You can freely add or delete all /32 addresses > > while not 200.46.204.2 and 200.46.208.2 > That's cool, since those IPs are just for the base server itself, and > never get removed ...