Michael Tüxen

Where is the TCP/IP source code located?

@nbriggs Thanks for the information. I was looking for the TCP code and did not find it... I have not idea what PUP and XNS is, I was just wondering...

> It followed pretty closely the design of the BSD stack from the early ‘80s, but implemented in Interlisp-D to work on 10-Mb Ethernet. With the transition to non-Xerox hardware...

> @tuexen -- PUP => PARC Universal Packet, the packets on the original 3 Mb ethernet (http://www.bitsavers.org/pdf/xerox/parc/techReports/CSL-79-10_Pup_An_Internetwork_Architecture_Jul79.pdf), and XNS => Xerox Network Services, the packets on the 10 Mb ethernet....

> You're more than welcome to check out the old code that you'll find from the git whatchanged command I mentioned above. I _am_ looking to get the BPF interface...

SCTP will perform PMTUD, however it does need to control the DF-bit via the DTLS API. This is not yet supported by OpenSSL, I think. Also an improved PMTUD algorithm...

> On 19. Jun 2017, at 10:58, Lennart Grahl wrote: > > Okay, so if it cannot set the DF-bit it's useless? Will it work if I circumvent the DTLS...

In the tracefile you showed, there are no ACKs. So if there are actually no acknowledgements, this trace is fine, if the Nagle algorithm is disabled. Please note, that TCP...

> README of uperf already makes it clear that it is _flexible_ - this issue is about wether it is as efficient and _similarly_ flexible as flent. > Sorry if...

> Quoting Michael Tüxen (2020-11-17 17:17:40) > > * Can uperf provide machine-readable output both for the server and the client end? Depends on the notion of "machine-readable". > Care...