[MirageOS-devel] mirage-tcpip Fin/Fin-Ack

[Hannes Mehnert <hannes@xxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Hey,

first of all: thanks for your great work on mirage. It is an awesome
project.

While writing some mirage code, I discovered that the TCP layer sends
a duplicate ack after a fin (which is fin + ack):

client --SYN-(seq=0)-> mirage
mirage --SYN-ACK-(seq=0,ack=1)-> client
client --ACK-(seq=1,ack=1)-> mirage
client --data-(seq=1,len=7)-> mirage
mirage --FIN-ACK-(seq=1,ack=8)-> client
mirage --ACK-(seq=2,ack=8)-> client
client --ACK-(seq=8,ack=2)-> mirage
client --FIN-ACK-(seq=8,ack=2)-> mirage
mirage --ACK-(seq=2,ack=9)-> client


This happens already with the network-skeleton/network code, running
on unix (FreeBSD) with a tap interface. I've uploaded a pcap file with
the tcp connection to https://berlin.ccc.de/~hannes/mirage-network.pcap .

Unfortunately I wasn't able to spot the piece of code responsible for
sending the duplicated ack.


Any ideas on this issue?

Hannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQIcBAEBCQAGBQJS/5BjAAoJELyJZYjffCjut2kQALsAIFUa722YpORNLDCj059T
TjnyWgnXM8pXhTX7sKRJ4E60ke0uC4FGxowwm6TSZ36iUPibKcoBkURDisinsxmE
U5uu3fJoJipcxmS0FTtap6eQ9RcfoOAV3Y+LmLw6w9C2je3uFAgg/VVUZLFqOTvZ
AsrUiUu6C5ET23ajogBZyvYKtxU26KWrdkTI7zjCY8Xc6gQgTuDIcg31Y+bm+p53
U9leqKMWDhrcaHOTgNt2tSTAeBYX46lNc+A79PgJhor5FLPCB39cDaKuw/gBs71k
+d92uTfDIW3Ehcm2/ecmzYhuM/zXR41IHcqqhlM/woXJfK3t6tdEbv4azV/LlE6z
nPitFGIdS4cPefiZKtEj+a4Nost8xj2HtVZpsqlFa+mEe8diNU7K6sEIlJzO5p8f
KkkmiqNxgttLFBskIMmRUseWl506ckvY7TXoUg4kcU6OAF+0jBmj0XmJgf/5Lrfq
i5i2yrXggosI06Fu6fWdAKZs7BqiSmqsRkgl8fSkN4i4jvzRTCXWUqrM+eydl19n
UbRPflr5mRiUwxkqAO3Qib9iTJSv5fuiy1dqar+Vo67v8BCD3vaYhmLqP+vtuMwx
7FTL4jTD3mdqvwqHAlZ7GBRcfPJuscOdTWNuXE0yHkFg6yrwra1XSrNmx7kGVeue
zxEwFzoL4QA86lHlb4tj
=Q41d
-----END PGP SIGNATURE-----

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel