@joerg
Quote:
Are you using the RTL driver versions from os4welt.de with the workarounds for the QEmu RTL emulation bugs? The public versions (for real hardware) are unlikely to work without problems.
Yes, I use this driver. It works quite well for my purposes, and I have no complaints about it.
But it can also crash.
For example, if you start copying a large number of very small files (such as program sources via RNOXfer), the driver will stop working.
But I've learned how to use it.
Quote:
You may manually have to reduce the MTU/MRU sizes as a router adds some overhead causing packet splits for connections outside of the LAN if you use the max. MTU/MRU sizes supported by your LAN.
IIRC MTU path discovery doesn't work or isn't even implemented in RoadShow and the only AmigaOS TCP/IP stack supporting it was the "Deluxe" version of Miami (MiamiDx)
MTU cannot be changed to AOS4 above the value of 1500. Above this value, e.g., 9000, they change to 1500.
It is possible to change something using Roadshowcontrol.
Changing the tcp.sendspace/tcp.recvspace value to the minimum value with the virtio-net.device driver causes a very quick “TransmitPacket: TX timout ..” error.
I don't really know where this comes from and where the value 1000000 comes from.
I tried on the qemu side and with the virtio-net-pci options to limit the RX buffer and speed, but it didn't help.
But as I wrote, after the error “TransmitPacket: TX timout ..” appeared, the driver
It still works. Something has stifled it.
I have no idea how to quickly clear buffers in AOS4, reset certain things like in Linux. It's hard to find any documentation for AOS4.
The virtio-net.device driver is definitely faster than RTL8139.
Maybe the symptoms show up faster, but is that a problem with the early version of the virtio-net.device driver?
I'll play around with it some more
