11-06-2008
Try :
# snoop -v -i /tmp/dhcp-snoop.snp | grep UDP:
Last edited by nam.nguyen; 11-06-2008 at 10:59 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
Users are connecting thru a KCML Client to UNIX machine, and I want to know which TCP/UDP port that client uses? How can I check the port of a user logged in?
Regards,
Tayyab (2 Replies)
Discussion started by: tayyabq8
2 Replies
2. Infrastructure Monitoring
hi guys
My linux server have SNMP configure port by default is 161 (UDP)
now my monitor team - who are using Nagios - say the server are not being monitor
so check netstat -lnu and I see all is OK and snmp service is running fine
what else should I check about this port 161? to see if it is... (0 Replies)
Discussion started by: karlochacon
0 Replies
3. AIX
May I know what is the TCP/UCP port range for any default AIX NFS? Based on rpcinfo -p, I got the following output:
program vers proto port service
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100000 4 ... (4 Replies)
Discussion started by: famasutika
4 Replies
4. Programming
Hello,
I'm trying to write a small c application to test a tcp port. This works fine for the most part but the default timeout on the connect is very long. I have been reading many posts but and it looks like I need to set the socket to be non-blocking and poll for a result. I have been totally... (2 Replies)
Discussion started by: tjones1105
2 Replies
5. IP Networking
Hi ,
Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (0 Replies)
Discussion started by: prabakar4all
0 Replies
6. Red Hat
Hi ,
Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (1 Reply)
Discussion started by: prabakar4all
1 Replies
7. IP Networking
Hi,
I am trying to set up a dev environment and I have Ubuntu server (10.16.1.92) and a CentOS VM (10.16.3.235) on this. On the CentOS I have a program running on port 5433. Now my problem is that I am unable to telnet this port from another Windows server whereas I can telnet port 22 from... (5 Replies)
Discussion started by: rishav
5 Replies
8. Shell Programming and Scripting
We have open port UDP port 31011, how to verify if port were working or traffic were receive. (2 Replies)
Discussion started by: avtalan
2 Replies
9. UNIX for Dummies Questions & Answers
I want to test the connectivity to an IP with Port number = xxxx.
I only know telnet can do it. For example, telnet <IP> <port>.
But I don't have telnet installed (no package) on my Red Hat Linux server.
I searched the Internet and realized that I will need either the installation media which... (2 Replies)
Discussion started by: learnix
2 Replies
10. Shell Programming and Scripting
Hello,
I am pretty unskilled in bash and I need some script and my skills ale limited (yet) I am learning but situation now needs some more skills.
is there possibility to simply check IP address with ports from csv file?
My csv has hundred of IPs in this format
... (9 Replies)
Discussion started by: Keagan
9 Replies
LEARN ABOUT MOJAVE
newproc.d
newproc.d(1m) USER COMMANDS newproc.d(1m)
NAME
newproc.d - snoop new processes. Uses DTrace.
SYNOPSIS
newproc.d
DESCRIPTION
newproc.d is a DTrace OneLiner to snoop new processes as they are run. The argument listing is printed.
This is useful to identify short lived processes that are usually difficult to spot using traditional tools.
Docs/oneliners.txt and Docs/Examples/oneliners_examples.txt in the DTraceToolkit contain this as a oneliner that can be cut-n-paste to run.
Since this uses DTrace, only users with root privileges can run this command.
EXAMPLES
This prints new processes until Ctrl-C is hit.
# newproc.d
FIELDS
CPU The CPU that recieved the event
ID A DTrace probe ID for the event
FUNCTION:NAME
The DTrace probe name for the event
remaining fields
These contains the argument listing for the new process
DOCUMENTATION
See the DTraceToolkit for further documentation under the Docs directory. The DTraceToolkit docs may include full worked examples with ver-
bose descriptions explaining the output.
EXIT
newproc.d will run forever until Ctrl-C is hit.
AUTHOR
Brendan Gregg [Sydney, Australia]
SEE ALSO
execsnoop(1M), dtrace(1M), truss(1)
version 1.00 May 15, 2005 newproc.d(1m)