05-16-2017
Any garbage computer plus a PCI ethernet card beats a pi with a USB, with bonuses of being cheaper, faster, easier to use, able to boot a normal Linux livecd, able to run a distribution anyone has actually heard of, able to use media besides sd cards, and able to support normal hardware.
That you can do anything with a pi doesn't mean you should...
Last edited by Corona688; 05-16-2017 at 03:46 PM..
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
there are commands to monitor the memory, paging, io... how about network traffic. i mean commands to see whether the network traffic (LAN) is congested? the closest i got is netstat
thanks (6 Replies)
Discussion started by: yls177
6 Replies
2. Cybersecurity
Hi,
Can someone give me the clue on how to capture network traffic at gateway.
Thanx (2 Replies)
Discussion started by: kayode
2 Replies
3. Programming
I am developing a Network Appliation to monitor computers in a network.
Specs are
App monitors the current web page viewed in each system
App also can shutdown the computer in the network
App can show all process run by each computer in the network
I am now confused how to start my... (2 Replies)
Discussion started by: valaparambil88
2 Replies
4. Infrastructure Monitoring
Hi all,
Got a strange one here, well not so much strange, different :-)
I need to work out if a server is particulary chatty, whether its talking / communicating heavily to a particular server, as Im planning to physically move the server to a different server, over a link. Hence the... (6 Replies)
Discussion started by: sbk1972
6 Replies
5. HP-UX
I Colleagues,
Somebody can say me how to monitoring traffic in the network. also I am interested in monitoring memory. if somebody to know a guide with command advanced in unix welcome for me.
Thank you for adcanced. (0 Replies)
Discussion started by: systemoper
0 Replies
6. Red Hat
How to monitor network device traffic using MRTG?
How can I add network devices in MRTG configuration to monitor? (2 Replies)
Discussion started by: manalisharmabe
2 Replies
7. UNIX Desktop Questions & Answers
Hello,
I am working in office, where, more than 60 clients machines (only 16 machines are on windows) are there and one server Centos Server, I have configured clients with server, so that internet will be used form only one IP. Only 1 ip is assigned, but now a days, my client machines are... (2 Replies)
Discussion started by: RedRocks!!
2 Replies
8. Infrastructure Monitoring
If I would like to know what connection , data , traffic in a network port ( eth0 ) , what can I do ?
ps. because I always found the network is very slow , so I would like what the network port is doing .
Thanks
Login ID ust3 is currently in read-only mode for multiple infractions. Creating... (0 Replies)
Discussion started by: ust03
0 Replies
9. UNIX for Advanced & Expert Users
Hi All
I am resilience testing an application that is spread across multiple servers.
One thing I will need to do soon is throttle the network traffic for specific interfaces within the test cluster. Specifically, maybe make a connection take twice or three times as long to respond....
I... (3 Replies)
Discussion started by: bbq
3 Replies
LEARN ABOUT REDHAT
axnet_cs
AXNET_CS(4) Kernel Interfaces Manual AXNET_CS(4)
NAME
axnet_cs - Asix AX88190 chipset PCMCIA Ethernet Driver
SYNOPSIS
insmod axnet_cs.o [pc_debug=n] [irq_list=i,j,...]
DESCRIPTION
Axnet_cs is a driver for PCMCIA ethernet cards based on the Asix AX88190 chipset. These cards are mostly NE2000 compatible but have sev-
eral bugs that are sufficiently tricky to work around that a separate driver was deemed necessary. When this driver is bound to a card, it
allocates the next available ethernet device (eth0..eth#). This device name will be reported in the kernel log file, and passed on to
cardmgr(8).
PARAMETERS
pc_debug=n
Selects the PCMCIA debugging level. This parameter is only available if the module is compiled with debugging enabled. A non-zero
value enables debugging.
irq_list=i,j,...
Specifies the set of interrupts that may be allocated by this driver.
DIAGNOSTICS
axnet_cs: this is not an AX88190 card!
Indicates that this card is probably a normal NE2000 compatible card, which requires the pcnet_cs driver.
eth#: interrupt(s) dropped!
Indicates that the driver did not receive an interrupt notification for some reason. The driver will poll the card (with a signifi-
cant performance penalty) if the problem persists. The most likely cause is an interrupt conflict and/or host bridge configuration
problem.
AUTHOR
David Hinds - dahinds@users.sourceforge.net
SEE ALSO
cardmgr(8), pcmcia(5).
pcmcia-cs 2001/08/17 12:51:58 AXNET_CS(4)