Hi all
Does anyone have any experience of using USB 2.0 to ethernet adaptors? Ignoring the apparently magical ability to get more than 280 Mbits/s of adaptors advertised as "USB 2.0 to gigabit ethernet", what is the realistic maximum throughput anyone has experienced with such devices, and on what architectures?
I am considering options for building a very small, low powered in-line F/W and some of the devices I am looking at only have one ethernet port (but often two or more USB ports).
Any and all advice (up to and including "don't be silly, do it properly") happily accepted.
Cheers
Mick
---------------------------------------------------------------------
blog: baldric.net gpg fingerprint: FC23 3338 F664 5E66 876B 72C0 0A1F E60B 5BAD D312
---------------------------------------------------------------------
On 08/04/13 20:32, mick wrote:
Hi all
Does anyone have any experience of using USB 2.0 to ethernet adaptors? Ignoring the apparently magical ability to get more than 280 Mbits/s of adaptors advertised as "USB 2.0 to gigabit ethernet", what is the realistic maximum throughput anyone has experienced with such devices, and on what architectures?
I am considering options for building a very small, low powered in-line F/W and some of the devices I am looking at only have one ethernet port (but often two or more USB ports).
I'm not sure about the potential bandwidth you'll likely achieve but what I will say is that USB interfaces and devices are CPU bound..so CPU usage will grow with network traffic faster than it would if you had a "real" NIC.
On a modern PC it isn't so much that you'd notice...on a small embedded system such as you may be using for this project it will become a factor, particularly if more than one interface is in use.
Also watch out because some (and one very popular *cough*) low power embedded systems already have their internal NIC hanging off a USB interface...the bandwidth isn't per port it's per controller bus, of which anything small and low power is only likely to have one.
On Mon, 08 Apr 2013 21:26:58 +0100 Wayne Stallwood ALUGlist@digimatic.co.uk allegedly wrote:
On 08/04/13 20:32, mick wrote:
I am considering options for building a very small, low powered in-line F/W and some of the devices I am looking at only have one ethernet port (but often two or more USB ports).
I'm not sure about the potential bandwidth you'll likely achieve but what I will say is that USB interfaces and devices are CPU bound..so CPU usage will grow with network traffic faster than it would if you had a "real" NIC.
On a modern PC it isn't so much that you'd notice...on a small embedded system such as you may be using for this project it will become a factor, particularly if more than one interface is in use.
Also watch out because some (and one very popular *cough*) low power embedded systems already have their internal NIC hanging off a USB interface...the bandwidth isn't per port it's per controller bus, of which anything small and low power is only likely to have one.
Wayne
Thanks for the input (and thanks also to BJ).
The device I am currently playing with is a sheevaplug. Not fantastically fast, but a lot faster than my NSLU2s and the pi. I haven't yet tested it in anger because I'm still building the thing (probably shorewall).
The generic chinese 10/100 USB adaptor I bought (my network runs at 100Mbits/s) *just works* when plugged in to the sheevaplug (running debian squeeze.) It runs noticeably very hot - not sure if that is normal.
Cheers
Mick ---------------------------------------------------------------------
blog: baldric.net gpg fingerprint: FC23 3338 F664 5E66 876B 72C0 0A1F E60B 5BAD D312
---------------------------------------------------------------------
-
mick -
Wayne Stallwood