Interesting...unfortunately I think I fall into the same problem you
did. Ah well, something to think about for other projects I suppose.

Thanks,

Josh
--
A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete
fools.
        -Douglas Adams

Dale Botkin wrote:
>
> Yep.  Now on its way to its new owner.  Like I said, it's not perfect for
> every application -- in my particular case, I needed something that would
> enable me to asynchronously send UDP packets over large IP networks.  The
> show stopper was the IP stack -- it's designed as a web server that has a
> lot of interfacing ability.  One thing they did that's pretty interesting
> is to eliminate the need for a default gateway and ARP protocol -- the SP
> simply sends all reply packets to the same IP and MAC address from which
> the request was received.  Note that this means if you didn't receive a
> request, you've got a problem.  Works fine for a web server, but in my
> case I wanted to be able to send a UDP packet to a known IP address.
> There is a way to do it but it requires that you know the IP *and MAC*
> address of the target host.  As this was going to be a commercial product,
> making the user enter the MAC address of the gateway or host was really
> not acceptable.  I needed ARP at least, so it wouldn't work for my
> particular application.  For many remote control/status applications,
> though, it would be fine.

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.