Mswale-I agree with you. I was doing enterprise networks in 1990, doing token ring, Ethernet, and AppleTalk. I learned and mastered the Network General’s Sniffer where I could look at what was going on in each network. I could see the whole IP packet with all the associated metadata.
When somebody tells you they modified the structure of an IP packet, that’s BS. If you do this nothing will work. When dealing with data, the standard mtu is 1500 bytes. When I was streaming large database data, I was using jumbo frames which increased efficiency in a WAN environment. If I was doing 4K streaming I would try using jumbo packets, but for music, the standard mtu is fine.
1 more thing, there is nothing to a switch, it forwards packets to a destination which can be another switch, router, or a device. Do a trace route to see how many hops you go thru getting to tidal/qobuz/google.
All the work happens on both ends of the route, not the switch itself. My switch is more of an enterprise switch where it doesn’t use a wall wart, and I’m using a few hundred $$ power cable into the switch
I also agree with the poster that i2s is the best interface. My streamers job is to change the signal path from Ethernet coming in to i2s going out.