Re: arbitrary packets on an ethernet network

BQ wrote:

(snip)

In the case I will opt for a standard protocol, which transport-layer protocol would you suggest in order to send commands, small amounts of data and retrieve information (e.g. retrieve the temperature read by a sensor, send a start / stop command to a device, etc)? For example, I think that TFTP is not ideal for this kind of job.

UDP. TFTP is UDP based, but that doesn't mean you need to do anything
like that.

To make it more simple, if you can rely on both being on
the same subnet you can leave out routing code (at least for the
first try). You should really include it, at least with static
routing. In the end, it won't be much different than doing
your own protocol. When you receive a packet in the buffer,
exchange the source and destination MAC addresses, IP addresses,
and ports, extract the incoming data, store the outgoing
data, and send it out. You should compute the appropriate
checksum, but it is optional for UDP.

I believe you are supposed to be able to process at least
a 576 byte packet, but if you don't need that you can probably
ignore that one, too.

You might try comp.protocols.tcp-ip for continuing discussion.

-- glen

.