--FL5UXtIhxfXey3p5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 03, 2003 at 12:21:20AM +0200, Manuel Bouyer wrote:
> On Wed, Apr 02, 2003 at 05:14:36PM -0500, Ian Thomas wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >=20
> > 	I have attempted to add a PC running NetBSD 1.6 to a hub with two=20
> > macs.  After doing the install, I brought up one of the interfaces,=20
> > ex0, and set it as follows
> >=20
> > ifconfig ex0 192.168.3.0
> >=20
>=20
> You can't use this address. 0 (and with usual 0xffffff00 netmask, 255) are
> reserved for broadcast addresses. Use something else (192.168.3.3 for
> example).

This is conventional wisdom, and on the safe side... but only necessary
if you have Really Old Broken Software anywhere on that network segment.

(Some early BSD variant would use all 0 instead of all 1 for broadcast.)

Even SunOS 4.1.1 can be configured to conform to the standard.

If it is any recent MacOS, I would be very surprised it it had this bug.

Hm ... ah, found it.

We have a compat switch to be backwards "compatible" to those broken=20
hosts, but you can switch it off via a sysctl:

Check if you have:

net.inet.ip.hostzerobroadcast =3D 1

If yes, set it to 0 and you're fine, I guess.

Regards,
	-is

--FL5UXtIhxfXey3p5
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: 2.6.i

iQEVAgUBPovyBzCn4om+4LhpAQHAVAf6A4ogiU95jzQ9LJlngY1zmGAtMtT5bM44
+0tY6kHIKKvgPKjJsKBn6D4aMZ2OQ6ENh2eA7rZjd1O2FTWjWUQWes0NlVG/jjsP
drVwNu9/Z+UlU1/QTNRTt2u6H5UM2YOQDTJWq3qJI9GVjC3C5ODSY/vqTM/2XGsY
IqcAx0R34dBMJ1XG+aytaMQUzIG4VoYr4rCCF5en4+IjT0qvM8TOO7bjSStdJb6o
RAThfLEkc5DB0UtKkz7FQ9vHgC7dgzprJoUxrB8mhDIMeCzbCxQpwKlq74N/Zin+
7zlDhgDfMWp0Ka5ZY30qgRzmpzfDUx7qE4HlVb8nQVgpsO7WuHGneQ==
=8hGZ
-----END PGP SIGNATURE-----

--FL5UXtIhxfXey3p5--