Raspberry Pi 4 released

just as an aside here, I've found that the most performant way of setting this is to have the native ethernet port do Access-Point/LAN duty, and the usb to ethernet adapter for the WAN side. Thereafter, use SQM for the WAN link to configure proper queueing. LAN side benefits from MQ fq_codel qdisc setup on the eth0, and the pitfalls/limitations of the adapter are mitigated by leveraging CAKE and SQM-scripts for proper queue management rather than relying on falling back to BQL.Haven't seen this noted explicitly anywhere , so felt it might help others. Took me an inordinate amount of testing to properly establish these things. This was more to properly establish the fine-grain performance and optimize, actual throughput at maximum levels is fine mostly irrespective of this. I'd also suggest disabling all network offloading with ethtool on eth0 and eth1 if you've a connection below 100mbit, adds additional complexity that potentially adds latency to no real benefit.