-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix TCP support #89
Comments
Kommer ihåg att ett problem vi hade var att med 3c509 så var man manuellt tvungen att lägga en Ethernet checksum crc32 i slutet av ethernetframen. :)
Det löste problem med att ingen ville ta emot våra paket. Andra nätverkskort la automatiskt på checksum...
…---
Henrik Doverhill
Ägare och produktchef, Caspeco AB
________________________________
From: Per Lundberg <notifications@github.com>
Sent: Wednesday, March 22, 2017 5:54:46 AM
To: chaos4ever/chaos
Cc: Subscribed
Subject: [chaos4ever/chaos] Fix TCP support (#89)
Subject says it all. The ipv4 server should be able to receive and send TCP packets.
This is a bit hard, since the TCP protocol is fairly complex, but we should at least be able to handle non-fragmented packages at first.
We did some initial experimentation around this in 2000 or 2001, but the problem back then was that the TCP packages we sent from chaos was never properly ACK:ed by the other machine. So the reason for this could be something like: bad checksum, problems with the packet structure, etc. It looked correct when we inspected the package with tcpdump and similar, but it still didn't work.
This bug has been bothering me for years and hopefully, we could sort it out eventually. 😄
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#89>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABYvu41nA5S-lXtyDgFJ7-AiCKsnwJalks5roKmWgaJpZM4MkueB>.
|
😄 I didn't remember that part, no. But like you say, it solved the problem with the ethernet checksum. I think there is also a TCP checksum, that we supposedly (?) give the right value, it doesn't show anything weird in Will have to dig into this, any decade now. 😉 |
Btw, I think it's actually not a CRC32 but a CRC16 in fact. 😆 |
Subject says it all. The
ipv4
server should be able to receive and send TCP packets.This is a bit hard, since the TCP protocol is fairly complex, but we should at least be able to handle non-fragmented packages at first.
We did some initial experimentation around this in 2000 or 2001, but the problem back then was that the TCP packages we sent from
chaos
was never properly ACK:ed by the other machine. So the reason for this could be something like: bad checksum, problems with the packet structure, etc. It looked correct when we inspected the package withtcpdump
and similar, but it still didn't work.This bug has been bothering me for years and hopefully, we could sort it out eventually. 😄
The text was updated successfully, but these errors were encountered: