Date: Sat, 22 Sep 2007 09:47:15 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: "Len Gross" <sandiegobiker@gmail.com> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: Multiple NICs - custom protocol development Message-ID: <446422errw.fsf@Lowell-Desk.lan> In-Reply-To: <27cb3ada0709202222w7af08809s2e7c8d79c5c7880b@mail.gmail.com> (Len Gross's message of "Thu\, 20 Sep 2007 22\:22\:21 -0700") References: <27cb3ada0709161413i163d942cld279e92634d06001@mail.gmail.com> <448x71nfmx.fsf@Lowell-Desk.lan> <27cb3ada0709202222w7af08809s2e7c8d79c5c7880b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Len Gross" <sandiegobiker@gmail.com> writes: > First, thanks for the response; It's nice to see some community support. > > Here is what I am trying to do: > > I am building a custom MAC protocol for a wireless system that has different > software on > the "head end" and the "clients." It is not peer-to-peer, While the > hardware is being developed > I want to use Ethernet as a physical layer. > > So,I want to use one card running server code and one card running client > code initially. Later I will do > the checkout with multiple client machines and a single server. > > If the OS "loops a packet back" (At the IP layer) before it gets to my "MAC > layer" then I can't test any code. If the client and server are sharing an IP stack, then the packets *should* be looped back at the IP layer. You want separate stacks for testing with IP, and in my earlier message I listed some ways to do that with a single machine. Getting a second PC is always an option too, and often a simple answer. Another option could be to fake (or wrap) the socket calls, but I doubt that's really going to be worthwhile for you. I prefer to never spend more time debugging the testbed than absolutely necessary. Good luck.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?446422errw.fsf>