The Amiga Future 146 was released on the September 3rd.
Amiga Future Aktion: Probeheft für 1 Cent
Im Augenblick gibt es im Shop unter https://www.amigashop.org die Möglichkeit ein Probeheft der Amiga Future für 1 Cent (+ Versandkosten, inkl. MwSt.) zu bestellen.
Amiga Future Promotion: Sample issue for 1 cent
We have a special offer for all of you who’ve gotten a taste of it: Right now you can order an Amiga Future issue for 1 cent (plus shipping costs and included VAT) at https://www.amigashop.org.
Gamescom Digital: https://gamescom.amigafuture.de
8 posts • Page 1 of 1
I'm debugging some network issues with Roadshow when used on the ZZ9000 and I'd like to clarify some behaviour?
Is roadshow rejecting received packets larger than the MTU?
The behaviour I'm seeing is that if I set my MTU to 500, then `ping -s 600 <dest>` the destination will successfully receive the packet split over 2 packets. The combined size is less than destinations MTU, so it returns the response in a single packet larger than the Amiga's MTU. This never makes it back to the application layer on the Amiga (I see it at the ethernet layer).
This should be fine - MTU should only be used for the transmission - but I've a feeling Roadshow may be using the value for the MRU (maximum receive unit). If this is the case, can it be fixed, or is there an interface option to set the MRU independently? If this isn't the case, I'll have to dig further into the whole stack.
Miami uses TCP/IP stack code which is at least 4-5 years younger than the one used by Roadshow. As things stand, the Roadshow TCP/IP stack makes no distinction between the maximum transmission unit and the maximum receive unit sizes. Each network interface only has a single maximum transmission unit record which governs both transmission and reception alike.
The other thing that might be a problem here is that the TCP/IP stack used by Roadshow lacks a feature known as "path MTU discovery" which allows packets to be fragmented and reassembled depending upon what the intermediate systems between your Amiga and remote hosts prefer. Normally, fragmentation issues are flagged through error messages passed up the transmission path, but not every TCP/IP stack along the way can adjust to the limitations reported. I'm sorry, but this is how things are for now
Thanks Olsen, that's a shame. Is there any hope that support for this can be added to the roadmap for a future fix?
As it stands, if the Amiga has an MTU set less than any other machine on the network it can drop valid packets. It wouldn't need path MTU discovery enabled, even just allocating a constant 1500 bytes for the RX buffer, irrespective of configured MTU, and capping received packets at that (the max for TCP within a normal ethernet frame), would fix it.
Also, slightly off-topic, but would you be open to adding support for hardware TCP/IP/UDP checksum offloading in the future? The ZZ9000 ethernet hardware supports it, and there seems to be unused ios2_Flags bits free in the SANA-II spec that could be used to both signal the device supports it and to pass back checksum results. Would need some alignment across the Amiga hardware community, but pretty sure everyone would be keen as it could lower the CPU overhead of network traffic.
This is a tough one... The TCP/IP stack code which Roadshow uses was used in NetBSD, OpenBSD, FreeBSD, etc. at the time and the newer features which were added to these operating systems might be portable. A while ago I specifically downloaded the earliest versions of NetBSD which followed the 1994 release of the TCP/IP stack which Roadshow uses. I made little progress there, though.
Limiting the MTU is still an option. Editing the respective network interface configuration file should be the easiest approach to do this.
Working out how the feature could be used is still an unsolved problem. At the minimum, you would have to let the TCP/IP stack know that the incoming datagrams need not be checked because the hardware already took care of that. This would already help The more difficult other half of the job is letting the TCP/IP stack know early on that it need not update the datagram and TCP/UDP checksums. There will be a point in the routing process which assigns a packet to a network interface at which the decision to deal with the checksums will have to be made. I don't know where that happens yet.
So, there's still a lot of work to be done, has been for years. We discussed this during OS4 development several years ago but made no progress...
Thanks olsen! The MTU thing isn't an issue in practice for me - I was only running at a smaller value to make it easier to dump the frames via kprintf and via the ARM code running on the ZZ9000 board in order to track down where some corruption was occurring.
As for a proof-of-concept for checksum offloading, I came across your https://github.com/obarthel/amiga-sana-ii-tftpclient project and finding it very useful for testing the idea and for also debugging the stack/.device/hardware flow of data in general. Thank you!
You're welcome This is exactly why I wrote the SANA-II tftpclient program: it's very hard to find a complete example code of how network client software works which talks to the SANA-II driver and which isn't 20-25 years old.
Did you make progress on your experiments? I am still pondering how to make hardware acceleration possible and so far I lack any test cases for it.
Can this be related to the 576 minimum datagram size? "The Internet Protocol requires that hosts must be able to process IP datagrams of at least 576 bytes (for IPv4)". The MTU is allowed to be as small as 68 bytes though. https://en.wikipedia.org/wiki/Maximum_transmission_unit