From owner-freebsd-net@FreeBSD.ORG Mon May 19 16:46:46 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85DAE106578D for ; Mon, 19 May 2008 16:46:46 +0000 (UTC) (envelope-from mwm@mired.org) Received: from mired.org (five.mired.org [66.92.153.75]) by mx1.freebsd.org (Postfix) with ESMTP id 09D748FC0A for ; Mon, 19 May 2008 16:46:45 +0000 (UTC) (envelope-from mwm@mired.org) Received: (qmail 3290 invoked from network); 19 May 2008 12:20:28 -0400 Received: from unknown (HELO mbook.local) (192.168.195.193) by 0 with SMTP; 19 May 2008 12:20:28 -0400 Date: Mon, 19 May 2008 12:20:00 -0400 From: Mike Meyer To: Jeremy Chadwick Message-ID: <20080519122000.526b2964@mbook.local> In-Reply-To: <20080519063133.GA54791@eos.sc1.parodius.com> References: <130587.38887.qm@web46316.mail.sp1.yahoo.com> <20080519063133.GA54791@eos.sc1.parodius.com> Organization: Meyer Consulting X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; i386-apple-darwin9.2.2) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org, John Timony Subject: Re: Net Mask Prob! X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2008 16:46:46 -0000 On Sun, 18 May 2008 23:31:33 -0700 Jeremy Chadwick wro= te: > On Sun, May 18, 2008 at 09:40:37PM -0700, John Timony wrote: > > Hi,all > > =C2=A0 > > I have installed Freebsd 7.0 on my Acer TravelMate 220,my router ip is = 192.168.0.1,the ip of my Freebsd is 192.168.1.4,Net Mask is 255.255.0.0,Why= my system can not connect wiht the router? > > =C2=A0 > > any idea? >=20 > Chances are your router uses 255.255.255.0 as a default netmask; most > residential routers do. FreeBSD doesn't have any issues/bugs relating > to netmasks which would cause what you're seeing. Freebsd should be using 255.255.255.0 as a default netmask for the 192.168 block as well. That's what it's defined to be. Changing that means fixing it everywhere. Also, as you get further from common setups, residential and soho routers tend to get flakier. Given that most users of such don't have hundreds of hosts and don't need two internal networks, a /23 in 192.168.0.0 qualifies as uncommon; it certainly gave me fits. I found that splitting the /24 into a pair of /25s worked better. > Additionally, your request probably should have gone to -net, not > -hackers. Yup.