Sponsored Content
Special Forums IP Networking I would like to monitor network traffic for a computer on my network Post 302998094 by cb88 on Thursday 25th of May 2017 12:42:28 AM
Old 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

monitoring network traffic

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

How to capture network traffic

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

Help in developing a Network Appliation to monitor pc in a network

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

Network Traffic

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

Monitoring traffic in the network

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 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

While Connecting to Google networking. Error = Unusual traffic from your computer network.

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

How do I know what traffic is in network port?

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

How to throttle network traffic?

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
dns(n)								Domain Name Service							    dns(n)

__________________________________________________________________________________________________________________________________________________

NAME
dns - Tcl Domain Name Service Client SYNOPSIS
package require Tcl 8.2 package require dns ?1.3.3? ::dns::resolve query ?options? ::dns::configure ?options? ::dns::name token ::dns::address token ::dns::cname token ::dns::result token ::dns::status token ::dns::error token ::dns::reset token ::dns::wait token ::dns::cleanup token ::dns::nameservers _________________________________________________________________ DESCRIPTION
The dns package provides a Tcl only Domain Name Service client. You should refer to (1) and (2) for information about the DNS protocol or read resolver(3) to find out how the C library resolves domain names. The intention of this package is to insulate Tcl scripts from prob- lems with using the system library resolver for slow name servers. It may or may not be of practical use. Internet name resolution is a complex business and DNS is only one part of the resolver. You may find you are supposed to be using hosts files, NIS or WINS to name a few other systems. This package is not a substitute for the C library resolver - it does however implement name resolution over DNS. The pack- age also extends the package uri to support DNS URIs (4) of the form dns:what.host.com or dns://my.nameserver/what.host.com. The dns::resolve command can handle DNS URIs or simple domain names as a query. Note: The package defaults to using DNS over TCP connections. If you wish to use UDP you will need to have the tcludp package installed and have a version that correctly handles binary data (> 1.0.4). This is available at http://tcludp.sourceforge.net/. If the udp package is present then UDP will be used by default. COMMANDS
::dns::resolve query ?options? Resolve a domain name using the DNS protocol. query is the domain name to be lookup up. This should be either a fully qualified domain name or a DNS URI. -nameserver hostname or -server hostname Specify an alternative name server for this request. -protocol tcp|udp Specify the network protocol to use for this request. Can be one of tcp or udp. -port portnum Specify an alternative port. -search domainlist -timeout milliseconds Override the default timeout. -type TYPE Specify the type of DNS record you are interested in. Valid values are A, NS, MD, MF, CNAME, SOA, MB, MG, MR, NULL, WKS, PTR, HINFO, MINFO, MX, TXT, SPF, SRV, AAAA, AXFR, MAILB, MAILA and *. See RFC1035 for details about the return values. See http://spf.pobox.com/ about SPF. See (3) about AAAA records and RFC2782 for details of SRV records. -class CLASS Specify the class of domain name. This is usually IN but may be one of IN for internet domain names, CS, CH, HS or * for any class. -recurse boolean Set to false if you do not want the name server to recursively act upon your request. Normally set to true. -command procname Set a procedure to be called upon request completion. The procedure will be passed the token as its only argument. ::dns::configure ?options? The ::dns::configure command is used to setup the dns package. The server to query, the protocol and domain search path are all set via this command. If no arguments are provided then a list of all the current settings is returned. If only one argument then it must the the name of an option and the value for that option is returned. -nameserver hostname Set the default name server to be used by all queries. The default is localhost. -protocol tcp|udp Set the default network protocol to be used. Default is tcp. -port portnum Set the default port to use on the name server. The default is 53. -search domainlist Set the domain search list. This is currently not used. -timeout milliseconds Set the default timeout value for DNS lookups. Default is 30 seconds. -loglevel level Set the log level used for emitting diagnostic messages from this package. The default is warn. See the log package for details of the available levels. ::dns::name token Returns a list of all domain names returned as an answer to your query. ::dns::address token Returns a list of the address records that match your query. ::dns::cname token Returns a list of canonical names (usually just one) matching your query. ::dns::result token Returns a list of all the decoded answer records provided for your query. This permits you to extract the result for more unusual query types. ::dns::status token Returns the status flag. For a successfully completed query this will be ok. May be error or timeout or eof. See also ::dns::error ::dns::error token Returns the error message provided for requests whose status is error. If there is no error message then an empty string is returned. ::dns::reset token Reset or cancel a DNS query. ::dns::wait token Wait for a DNS query to complete and return the status upon completion. ::dns::cleanup token Remove all state variables associated with the request. ::dns::nameservers Attempts to return a list of the nameservers currently configured for the users system. On a unix machine this parses the /etc/resolv.conf file for nameservers (if it exists) and on Windows systems we examine certain parts of the registry. If no name- server can be found then the loopback address (127.0.0.1) is used as a default. EXAMPLES
% set tok [dns::resolve www.tcl.tk] ::dns::1 % dns::status $tok ok % dns::address $tok 199.175.6.239 % dns::name $tok www.tcl.tk % dns::cleanup $tok Using DNS URIs as queries: % set tok [dns::resolve "dns:tcl.tk;type=MX"] % set tok [dns::resolve "dns://l.root-servers.net/www.tcl.tk"] Reverse address lookup: % set tok [dns::resolve 127.0.0.1] ::dns::1 % dns::name $tok localhost % dns::cleanup $tok REFERENCES
[1] Mockapetris, P., "Domain Names - Concepts and Facilities", RFC 1034, November 1987. (http://www.ietf.org/rfc/rfc1034.txt) [2] Mockapetris, P., "Domain Names - Implementation and Specification", RFC 1035, November 1087. (http://www.ietf.org/rfc/rfc1035.txt) [3] Thompson, S. and Huitema, C., "DNS Extensions to support IP version 6", RFC 1886, December 1995. (http://www.ietf.org/rfc/rfc1886.txt) [4] Josefsson, S., "Domain Name System Uniform Resource Identifiers", Internet-Draft, October 2003, (http://www.ietf.org/internet- drafts/draft-josefsson-dns-url-09.txt) [5] Gulbrandsen, A., Vixie, P. and Esibov, L., "A DNS RR for specifying the location of services (DNS SRV)", RFC 2782, February 2000, (http://www.ietf.org/rfc/rfc2782.txt) [6] Ohta, M. "Incremental Zone Transfer in DNS", RFC 1995, August 1996, (http://www.ietf.org/rfc/rfc1995.txt) AUTHORS
Pat Thoyts BUGS, IDEAS, FEEDBACK This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category dns of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for either package and/or documentation. SEE ALSO
resolver(5) KEYWORDS
DNS, domain name service, resolver, rfc 1034, rfc 1035, rfc 1886 CATEGORY
Networking COPYRIGHT
Copyright (c) 2002, Pat Thoyts dns 1.3.3 dns(n)
All times are GMT -4. The time now is 06:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy