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

On Sun, Apr 15, 2007 at 01:24:49AM -0700, Bryan Phillippe wrote:
> Hello,
>=20
> I would like to conduct some ethernet network testing using a NetBSD =20
> client & server configuration.  The unusual part about this is that I =20
> want my configuration to be a single NetBSD system functioning as =20
> both a client and a server, physically sending network traffic out on =20
> interface and back into another, using a cross-cable.

That won't really work. The problem is that NetBSD has one routing system.=
=20
You really need a system with two, one for one NIC and one for the other=20
NIC. The thing is that what is a local address for one routine system is a=
=20
remote address for the other, and our stack doesn't handle that.

I think something like Xen or Parallels or VMware would be the best way to=
=20
go. You'd then have two separate kernels & installations, each talking to=
=20
one of the NICs.

Take care,

Bill

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (NetBSD)

iD8DBQFGJPFjWz+3JHUci9cRAp1hAJwKATnoQvJLNLhxFky/FX3G8V3q8QCdFA3t
i4p67X1KR67onDxxlX5i0Dw=
=vgTE
-----END PGP SIGNATURE-----

--G4iJoqBmSsgzjUCe--