05-25-2017
Quote:
Originally Posted by
Corona688
pentium 4 is a bit old, unless it has 1g ram or more.
It's still more than 1-2 orders of magnitude faster than the original Pi. And probably 2-5x faster than a Pi2.
That said you could get a $2 USB Ethernet adapter on ebay ... and plug it into the pi and experiment with that. The Pi will probably show your internet down since it's peripherals all hang off it's overloaded USB bus.
The P4 ought to handle it with ease... as far as that goes lots of people have used much slower machines for routers/firewalls. Rather than using wireshark which is a rather heavy handed but comprehensive solution, you just do as suggested here with dnsmasq
How to log all my DNS queries? - Unix & Linux Stack Exchange
And filter the log for dnsmasq output.... just about as good as wireshark and probably more performant than running without the system as now your dns queries are cached by a local machine. The TCPDUMP answer there is also good.
If you get it working on the P4 getting a mini PC is probably a decent idea... as the power savings alone will pay for itself. A P4 computer costs between $100-300 a year to leave running vs the mini PC costing about 10 bucks a year.
Last edited by cb88; 05-25-2017 at 01:49 AM..
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 OSF1
niffconfig
niffconfig(8) System Manager's Manual niffconfig(8)
NAME
niffconfig - Configuration program for the Network Interface Failure Finder (NIFF)
SYNOPSIS
/usr/sbin/niffconfig [-a] [-m] [-r] [-s] [-u] [-v] [-d num] [-o num] [-t num] [interface1 interface2...]
OPTIONS
Adds an interface or interfaces, specified by the interface parameter. You cannot specify the -a option with the -m, -s, -r, or -u options.
Specifies the time period, in seconds, that the traffic monitor thread uses between reads of the interface counters when it suspects there
is a connectivity problem. This number must be smaller than the number given for the -t option. The default time period is 5 seconds. If
num is not specified, niffconfig uses the default. Specifies the total number of traffic-free seconds that must elapse before the traffic
monitor thread determines that a network interface has failed. This number must be at least the sum of the -d option and two times the -t
option. That is, given the default time period for -d and -t, the -o option must be at least 20 seconds. The default time period for this
option is 60 seconds. If num is not specified, niffconfig uses the default. Modifies the timing parameters of an interface that is already
being monitored. Typically, this option is specified along with one or more of -t num, -d num, or -o num options. If none of these parame-
ters are specified, the default value is used. You cannot specify the -m option with the -a, -s, -r, or -u options. Stops monitoring the
specified interface. Obtains the status of the specified interface. Specifies the time period, in seconds, that the traffic monitor
thread delays between reads of the interface counters when the network is running normally. The default time period is 20 seconds. If num
is not specified, niffconfig uses the default. Displays the status of all interfaces currently being monitored to standard out (stdout).
Displays the status, timer values, and description (verbose mode) of all interfaces currently being monitored to standard out (stdout).
DESCRIPTION
The niffconfig command arranges for one or more network interfaces to be monitored for possible loss of connectivity. Timing parameters
that govern how quickly an interface can be declared suspect or dead may be manipulated with this command. You can specify multiple inter-
faces, separated by a space, on the command line. Note, you must be superuser to use the niffconfig command.
Except for the -u and -u options, all niffconfig options require one or more network interfaces to be specified.
EXAMPLES
To add the tu0 and tu1 interfaces to the list of monitored interfaces, enter: # niffconfig -a tu0 tu1 To change the time it takes to
declare failure on the tu1 interface to 90 seconds, enter: # niffconfig -o 90 tu1 To display the status of all interfaces that are being
monitored: # niffconfig -u To stop monitoring the tu0 interface: # niffconfig -r tu0
SEE ALSO
Daemons: niffd(8)
Information: EVM(5), nifftmt(7)
niffconfig(8)