Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.arch.embedded > #27326

Re: Embedded Ethernet

From David Brown <david.brown@hesbynett.no>
Newsgroups comp.arch.embedded
Subject Re: Embedded Ethernet
Date 2017-09-24 13:28 +0200
Organization A noiseless patient Spider
Message-ID <oq84sh$ajp$1@dont-email.me> (permalink)
References <oq3bj1$btg$1@dont-email.me> <WNWdnXHLauJvy1jEnZ2dnUU7-UednZ2d@earthlink.com> <oq417s$h39$1@dont-email.me> <oq6gr4$fmk$1@reader2.panix.com> <CLydnbgSP8zPZlvEnZ2dnUU7-K2dnZ2d@earthlink.com>

Show all headers | View raw

On 24/09/17 02:24, Joe Chisolm wrote:
> On Sat, 23 Sep 2017 20:40:04 +0000, Grant Edwards wrote:
> 
>> On 2017-09-22, pozz <pozzugno@gmail.com> wrote:
>>
>>> I can choose. I know UDP is much smaller than TCP,
>>
>> UDP is also far less likey that TCP to make it safely through
>> firewalls and routers.
>>
>>> but I should add some TCP-features on top of UDP: mainly ack and
>>> retransmissions.
>>
>> If you're going to have to re-invent TCP, then just use TCP and avoid
>> all of the headaches you'll have with UDP and firewalls/routers.
> 
> TCP wont necessarly fix a firewall issue.  All depends on the
> firewall configuration for inbound traffic.  The firewall could
> be configured to allow UDP traffic to a specific dest addr/dest port
> For outbound many firewalls will allow a inbould UDP packet directed
> to the same src addr/src port that generated the outgoing packet.

Of course it all depends on the firewall setup.  And yes, you can get
UDP to work through firewalls.  But it is very difficult to get a
firewall setup that is secure and reliable, and safely lets through the
traffic you want and blocks traffic you don't want.  And it is even more
difficult when you have VPNs, tunnels, or other routes involved.  Such
routing is /really/ useful when you are testing and debugging network
systems - when you are sitting back in your office, connecting securely
to the customer network on the other side of the world, you will be glad
everything is running over TCP/IP.

> 
> But I agree if you need close to guaranteeded data delivery a TCP
> app is easier to build.  FreeRTOS/lwip is a reasonable choice.
> 
>

Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Embedded Ethernet pozz <pozzugno@gmail.com> - 2017-09-22 17:52 +0200
  Re: Embedded Ethernet mmm <m.colandrea@libero.it> - 2017-09-22 18:00 +0200
  Re: Embedded Ethernet David Brown <david.brown@hesbynett.no> - 2017-09-22 20:27 +0200
    Re: Embedded Ethernet pozz <pozzugno@gmail.com> - 2017-11-17 10:25 +0100
      Re: Embedded Ethernet Theo Markettos <theom+news@chiark.greenend.org.uk> - 2017-11-17 10:39 +0000
        Re: Embedded Ethernet pozz <pozzugno@gmail.com> - 2017-11-17 12:25 +0100
      Re: Embedded Ethernet "Boudewijn Dijkstra" <sp4mtr4p.boudewijn@indes.com> - 2017-11-17 11:36 +0100
        Re: Embedded Ethernet pozz <pozzugno@gmail.com> - 2017-11-17 12:54 +0100
      Re: Embedded Ethernet David Brown <david.brown@hesbynett.no> - 2017-11-17 15:23 +0100
      Re: Embedded Ethernet Mikko OH2HVJ <mikko.syrjalahti@nospam.fi> - 2017-11-18 11:29 +0200
  Re: Embedded Ethernet Joe Chisolm <jchisolm6@earthlink.net> - 2017-09-22 13:31 -0500
    Re: Embedded Ethernet pozz <pozzugno@gmail.com> - 2017-09-23 00:01 +0200
      Re: Embedded Ethernet raimond.dragomir@gmail.com - 2017-09-22 22:38 -0700
        Re: Embedded Ethernet raimond.dragomir@gmail.com - 2017-09-22 22:41 -0700
      Re: Embedded Ethernet David Brown <david.brown@hesbynett.no> - 2017-09-23 12:02 +0200
        Re: Embedded Ethernet Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2017-09-23 06:32 -0400
          Re: Embedded Ethernet Dimiter_Popoff <dp@tgi-sci.com> - 2017-09-23 15:31 +0300
            Re: Embedded Ethernet Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2017-09-25 13:07 -0400
              Re: Embedded Ethernet Robert Wessel <robertwessel2@yahoo.com> - 2017-09-25 15:31 -0500
                Re: Embedded Ethernet Dimiter_Popoff <dp@tgi-sci.com> - 2017-09-27 01:50 +0300
          Re: Embedded Ethernet Les Cargill <lcargill99@comcast.com> - 2017-09-28 20:07 -0500
        Re: Embedded Ethernet upsidedown@downunder.com - 2017-09-23 14:48 +0300
        Re: Embedded Ethernet Les Cargill <lcargill99@comcast.com> - 2017-09-28 20:06 -0500
          Re: Embedded Ethernet Joe Chisolm <jchisolm6@earthlink.net> - 2017-09-29 09:41 -0500
          Re: Embedded Ethernet upsidedown@downunder.com - 2017-09-30 18:49 +0300
        Re: Embedded Ethernet pozz <pozzugno@gmail.com> - 2017-10-12 11:26 +0200
          Re: Embedded Ethernet David Brown <david.brown@hesbynett.no> - 2017-10-12 12:46 +0200
          Re: Embedded Ethernet Joe Chisolm <jchisolm6@earthlink.net> - 2017-10-12 10:49 -0500
      Re: Embedded Ethernet Grant Edwards <invalid@invalid.invalid> - 2017-09-23 20:40 +0000
        Re: Embedded Ethernet Joe Chisolm <jchisolm6@earthlink.net> - 2017-09-23 19:24 -0500
          Re: Embedded Ethernet David Brown <david.brown@hesbynett.no> - 2017-09-24 13:28 +0200
  Re: Embedded Ethernet Les Cargill <lcargill99@comcast.com> - 2017-09-22 21:12 -0500
  Re: Embedded Ethernet Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2017-09-24 11:01 +0300
  Re: Embedded Ethernet pozz <pozzugno@gmail.com> - 2017-10-16 14:10 +0200
    Re: Embedded Ethernet David Brown <david.brown@hesbynett.no> - 2017-10-16 15:10 +0200
      Re: Embedded Ethernet pozz <pozzugno@gmail.com> - 2017-10-16 17:54 +0200
        Re: Embedded Ethernet David Brown <david.brown@hesbynett.no> - 2017-10-16 23:45 +0200
          lwip/httpd: how to return dynamic data [was Re: Embedded Ethernet] pozz <pozzugno@gmail.com> - 2017-11-13 12:11 +0100
            Re: lwip/httpd: how to return dynamic data [was Re: Embedded Ethernet] David Brown <david.brown@hesbynett.no> - 2017-11-13 14:14 +0100

csiph-web