People keep using raspberry Pi for things they're not suited for. The 100 Mbps Ethernet interface is attached to a USB2 bus. And it only has one ethernet port. Yes I suppose you could add a second interface by another USB dongle. If you really want to run wireshark and other stuff you're much better off with a really 1RU small x86-64 system that has two real Intel 1000BaseT NICs on board, and a couple of PCI-Express slots. Or a really small desktop thing if it's a non rack environment, like a mini-itx motherboard in a cube shaped case with an Intel-chipset 4x1000BaseT port card.
On Mon, Nov 13, 2017 at 9:28 AM, Steve Jones <[email protected]> wrote: > I have a voip pbx system issue im going to have to drop a long term > packet sniffer onto the network to catch an issue that only happens like > once in a month. So thats going to be alot of traffic (we have to capture > everything to see if the issue has to do with other network traffic, so I > cant even filter it out. > I was thinking about making a pi a sniffer and just hang a usb drive off > of it for the archive. > > I dont see running a sniffer would be all that great a resource drain. > > Any reason this would be a bad idea, i could see it being a good tool to > keep in our toolset. I just envision a little binder full of SD cards with > purpose builds and a handful of pis for a handy toolbox >
