From owner-freebsd-isp Thu May 11 7:20:42 2000 Delivered-To: freebsd-isp@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by hub.freebsd.org (Postfix) with SMTP id D95A737B564 for ; Thu, 11 May 2000 07:20:38 -0700 (PDT) (envelope-from up@3.am) Received: (qmail 39158 invoked by uid 1825); 11 May 2000 14:20:35 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 11 May 2000 14:20:35 -0000 Date: Thu, 11 May 2000 10:20:35 -0400 (EDT) From: X-Sender: up@richard2.pil.net To: blaine minazzi Cc: freebsd-isp@freebsd.org Subject: Re: Help with ifconfig please. In-Reply-To: <391AAF5E.76466444@denverweb.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 11 May 2000, blaine minazzi wrote: > I have posted this to the freebsd-questions, and now this is the second > post to freebsd-isp with this question. > > Surely someone knows tthe answer, and can help here. I have rtfm'ed > until my eyes bleed, and searched the newsgroups, mailing lists, etc. > > When I do as suggested, I get these problems. > > Here is the previous post. > =============================================================== > I am upgrading an older freebsd box to FreeBSD 4.0 stable. > > we will call it foobar.foo.com, and we will set up the ed0 device, > #ifconfig ed0 192.1668.1.1 netmask 255.255.255.0 > > default route is 192.168.1.254 > > When I do thusly, > > ifconfig ed0 alias 192.168.1.2 netmask 255.255.255.255 > ifconfig ed0 alias 192.168.1.3 netmask 255.255.255.255 > ---- snip out the ssdd stuff ------ > ifconfig ed0 alias 192.168.1.252 netmask 255.255.255.255 The netmask should be 255.255.255.0 > I get the following, at every OTHER invocation of ifconfig. > > May 9 14:38:14 foobar routed[79] possible netmask problem between > ed0:192.168.2.xx and ed0:192.168.1.0/24 ( where xx = every other ip > number. ) this message is repeated 3 times. > > > and this message also; > > May 9 14:38:14 foobar /kernel arp_rtrequest: bad gateway value > May 9 14:38:14 foobar last message repeated 17 times > May 9 14:39:38 foobar last message repeated 106 times > > Now, ifconfig shows that the ip's are indead bound to the card, and, I > can ping SOME of them, but some give me this error. > > /kernel: arplookup 192.168.1.143 failed: could not allocate llinfo > /kernel: arpresolve: can't allocate llinfo for 192.168.1.143rt > > then some more of these... > > /kernel: arp_rtrequest: bad gateway value > last message repeated 347 times > > > > So... what am I doing wrong here? > > Would someone please give me the correct magical spell to invoke? > > I would appreciate knowing the proper way to bind many ip's ( a /24 > actually ) to the card, so that when we place this in production, it > works correctly. > > Many thanks in advance. > > Blaine > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message