# Ethernet comms

**URL:** <https://boards.straightdope.com/t/ethernet-comms/289104>\
**Category:** In My Humble Opinion\
**Created:** [February 9, 2005, 1:45am UTC](https://boards.straightdope.com/t/ethernet-comms/289104 "2005-02-09T01:45:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Xema](https://avatars.discourse-cdn.com/v4/letter/x/9de053/32.png) [@Xema](https://boards.straightdope.com/u/Xema)\
**Post date:** [February 9, 2005, 1:45am UTC](https://boards.straightdope.com/t/ethernet-comms/289104/1 "2005-02-09T01:45:25Z")

</div>

I’ll soon be writing my first program (in C#, [VS.NET](http://VS.NET)) to do this - Windows PC talking to a remote single-board data-gathering computer. I’m seeking suggestions on tutorials that discuss the ins and outs of doing this.

---

<div class="post-metadata">

**Author:** ![ccwaterback](https://avatars.discourse-cdn.com/v4/letter/c/df705f/32.png) [@ccwaterback](https://boards.straightdope.com/u/ccwaterback)\
**Post date:** [February 9, 2005, 2:56am UTC](https://boards.straightdope.com/t/ethernet-comms/289104/2 "2005-02-09T02:56:57Z")

</div>

It will probably depend on what protocol your single-board computer will support. I would suggest something a bit higher on the networking hierarchy than Ethernet. Ethernet will work fine as your lower level protocol, but if you want make the communications channel much easier to deal with I would suggest an IP connection, or something at a much higher lever than Ethernet.

Depending on how and where this system has to work, you may develop your own protocol. You would need to program the single-board system to support your protocol too though.