On Sun, Mar 6, 2022 at 2:49 PM Peter C. Wallace <p...@mesanet.com> wrote:
> > The bottleneck with a shared Ethernet port is the MAC/Phy which would mean > outgoing and incoming real time packets might need to wait for normal > (large > packet) Internet traffic, adding considerable jitter. This is solved by > using a > separate physical interface. > Could not WiFi be used as the second network port? Of course one would have to set up routing such that the dedicated PC <--> Mesa network was on the Ethernet and the "default route" less the Mesa network was on WiFi. One other idea is to use the Linux "tc" command to place Mesa-bound packets to the top of the queue. Then set the packet length low. But this only works for PC to Meas packets A managed switch with traffic shaping would be a solution too, but USB/Ethernet dongles cost under $20 and managed switches $200+ > > > > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > -- Chris Albertson Redondo Beach, California _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
