From owner-freebsd-net Wed Jun 28 10: 3:44 2000 Delivered-To: freebsd-net@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id D35EC37B795 for ; Wed, 28 Jun 2000 10:03:40 -0700 (PDT) (envelope-from reichert@numachi.com) Received: (qmail 11390 invoked by uid 1001); 28 Jun 2000 17:03:35 -0000 Date: Wed, 28 Jun 2000 13:03:35 -0400 From: Brian Reichert To: freebsd-net@freebsd.org Subject: Re: Did IP aliasing change after 2.x? Message-ID: <20000628130335.E10407@numachi.com> References: <20000627192045.J1800@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <20000627192045.J1800@numachi.com>; from reichert@numachi.com on Tue, Jun 27, 2000 at 07:20:46PM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jun 27, 2000 at 07:20:46PM -0400, Brian Reichert wrote: > I have two servers running. > > 198.175.254.7 is running 2.2.7-RELEASE. > 198.175.254.4 is running 4.0-RELEASE. > > In each case, the IP is an alias on the NIC. > > From within my net, I can ping each of these name servers. From > outside of my net, I can only ping 198.175.254.7, the 'old' box. > > I can get to their primary IP addresses just fine. > > There is no packet filtering at play here. Just to respond to myself: _Part_ of the problem is a crappy switch; I took specific steps to 'populate' said switch's hash of MAC addresses via: ping -S 198.175.254.4 198.175.254.1 This against a few destinations on our net seemed to help. I can now make use of that server, even from outside our net. I don't understand why I was seeing this symptom, though: > On each of the newer box, when I dump ping traffic with > tcpdump: > > # tcpdump -n host 198.175.254.4 > tcpdump: listening on dc0 > 19:05:21.437187 208.176.83.163 > 198.175.254.4: icmp: echo request > 19:05:22.434743 208.176.83.163 > 198.175.254.4: icmp: echo request > 19:05:23.431832 208.176.83.163 > 198.175.254.4: icmp: echo request > > That network segment is getting packets destined for 198.175.254.4, > but the card never generates the 'echo reply' packets. But, for whatever magical reason, I'm all set now, so thanks for your patience... -- Brian 'you Bastard' Reichert reichert@numachi.com 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message