Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 May 2008 12:20:00 -0400
From:      Mike Meyer <mwm@mired.org>
To:        Jeremy Chadwick <koitsu@FreeBSD.org>
Cc:        freebsd-net@freebsd.org, John Timony <fabonacci@yahoo.com>
Subject:   Re: Net Mask Prob!
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>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 18 May 2008 23:31:33 -0700 Jeremy Chadwick <koitsu@FreeBSD.org> 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.

	<mike



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080519122000.526b2964>