Navigation
« 

Anonymous




Register
Login
« 
« 

Amiga Future

« 

Community

« 

Knowledge

« 

Last Magazine

The Amiga Future 167 was released on the March 5th.

The Amiga Future 167 was released on the March 5th.
The Amiga Future 167 was released on the March 5th.

The Amiga Future 167 was released on the March 5th.
More informations

« 

Service

« 

Search




Advanced search

Unanswered topics
Active topics
« 

Social Media

Twitter Amigafuture Facebook Amigafuture RSS-Feed [german] Amigafuture RSS-Feed [english] Instagram YouTube Patreon WhatsApp
« 

Advertisement

Amazon

Patreon

« 

Partnerlinks

Search found 4 matches

by chrisw
14.07.2020 - 23:23
Forum: Roadshow Support
Topic: Roadshow MTU and MRU
Replies: 12
Views: 10725

Re: Roadshow MTU and MRU

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 o...
by chrisw
06.07.2020 - 19:07
Forum: Roadshow Support
Topic: Roadshow MTU and MRU
Replies: 12
Views: 10725

Re: Roadshow MTU and MRU

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 cons...
by chrisw
02.07.2020 - 21:09
Forum: Roadshow Support
Topic: Roadshow MTU and MRU
Replies: 12
Views: 10725

Re: Roadshow MTU and MRU

I've just installed Miami and it doesn't display this behaviour. So looks like it's a Roadshow bug.
by chrisw
01.07.2020 - 23:41
Forum: Roadshow Support
Topic: Roadshow MTU and MRU
Replies: 12
Views: 10725

Roadshow MTU and MRU

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...