Richard Scheffenegger

Note that the tests fail, as all the test pcap file contain non-zero bits as reserved bits in the TCP headers. I'll try to fix these binaries to follow the...

> Since a packet analyzer's purpose is to display what is on the wire (even and especially if what's on the wire is not correct), it might be better to...

Note that the output of tcpdump with this patch is equivalent with the fork of tcpdump in MacOS, being used for dev work on AccECN there, as well as the...

> Since a packet analyzer's purpose is to display what is on the wire (even and especially if what's on the wire is not correct), it might be better to...

Thank you. Is that a request to further improve this pull request? Or for a subsequent one? Strictly speaking, these reserved bits are *NOT* MBZ (must be zero), but rather...

Should have written /* Release SCL to ensure that (repeated) Start can be performed */ DDR_USI_CL &= ~(1

Well, if you keep the PORT as output and set it high, the PIN will most likely read one - as you are injecting current not only via the (high...

> Thank you for waiting. Please find below some more comments regarding the proposed code changes. Sorry - apparently this response never reached me. > * The only change to...

When looking at the CI failures, it seems they fail due to some connectivity issues, but not the changes in this pull request... https://ci.appveyor.com/project/guyharris/tcpdump/builds/47615803/job/jswck707rky68qg3

I checked in a minor update to the man page. However, reading through this, I would like to understand where the parser code lives that interprets "tcp[tcpflags] & tcp-cwr !=...