Sponsored Content
Special Forums IP Networking how to identify network activity? Post 302302812 by pludi on Wednesday 1st of April 2009 05:51:11 AM
Old 04-01-2009
As root on Linux:
Code:
# netstat -anp

In the next-to-last column look for ESTABLISHED (won't appear for UDP). The last column gives you the PID and process name. If it's empty/'-' even as root, it's probably a mount.
 

7 More Discussions You Might Find Interesting

1. AIX

Disk activity

I'm new on UNIX and i want to display the LV NAME, LPs, PPs, DISTRIBUTION, MOUNT POINT but i don't know what is the command. Thanks, Regards (3 Replies)
Discussion started by: tovohery
3 Replies

2. AIX

Monitoring the network activity happening in a port in AIX 5.3

Hi All, I would like to monitor the volume of Data that is transferred through a single port in AIX. I have nmon installed in my machine. What is the best possible solution for this problem. Thanks in Advance. (3 Replies)
Discussion started by: bravo13
3 Replies

3. IP Networking

Illegal network activity

Hi, I have a wireless router connecting both windows and linux systems at home. I've discovered someone has been downloading illegal content on my network simply because they accidentally left the torrent downloader on their screen when showing me something. I removed their access for a few days... (1 Reply)
Discussion started by: neil999
1 Replies

4. Shell Programming and Scripting

need perl script to get a comprehend statistic of network activity in a LAN

need perl script to get a comprehend statistic of network activity in a LAN. The purpose is to get each indivisual data usages statistics so that I can determine who is doing the network congestion in terms of bandwidth usages both in real time and retrospectively.. Thanks in... (4 Replies)
Discussion started by: rrd1986
4 Replies

5. Hardware

identify wireless network card

hi Howto identify wireless network card using Live CD? (2 Replies)
Discussion started by: ccc
2 Replies

6. Shell Programming and Scripting

How to identify a network device before trying to connect to it?

Hello all, Here is the explanation of my problem: I have a cronjob that connects to a NAS to do backups from my laptop to this NAS device. The script that I wrote does check if there is a host (the NAS) responding on 192.168.1.10 and tries to connect to it with the following command: mount -v... (3 Replies)
Discussion started by: freddie50
3 Replies

7. Red Hat

Network activity log

I am having Red Hat Linux 5.9 installed in my server. There are 2 physical ethernet port in the server and these 2 ports are bonded to 1 bond0 port through linux bonding utility. For some days I am experiencing some fluctuation in server port. I want to analyze the same.How to do that? It may... (4 Replies)
Discussion started by: Anjan Ganguly
4 Replies
NSENTER(1)							   User Commands							NSENTER(1)

NAME
nsenter - run program with namespaces of other processes SYNOPSIS
nsenter [options] [program] [arguments] DESCRIPTION
Enters the namespaces of one or more other processes and then executes the specified program. Enterable namespaces are: mount namespace mounting and unmounting filesystems will not affect rest of the system (CLONE_NEWNS flag), except for filesystems which are explic- itly marked as shared (by mount --make-shared). See /proc/self/mountinfo for the shared flag. UTS namespace setting hostname, domainname will not affect rest of the system (CLONE_NEWUTS flag). IPC namespace process will have independent namespace for System V message queues, semaphore sets and shared memory segments (CLONE_NEWIPC flag). network namespace process will have independent IPv4 and IPv6 stacks, IP routing tables, firewall rules, the /proc/net and /sys/class/net directory trees, sockets etc. (CLONE_NEWNET flag). PID namespace children will have a set of PID to process mappings separate from the nsenter process (CLONE_NEWPID flag). nsenter will fork by default if changing the PID namespace, so that the new program and its children share the same PID namespace and are visible to each other. If --no-fork is used, the new program will be exec'ed without forking. See the clone(2) for exact semantics of the flags. If program is not given, run ``${SHELL}'' (default: /bin/sh). OPTIONS
Argument with square brakets, such as [file], means optional argument. Command line syntax to specify optional argument --mount=/path/to /file. Please notice the equals sign. -t, --target pid Specify a target process to get contexts from. The paths to the contexts specified by pid are: /proc/pid/ns/mnt the mount namespace /proc/pid/ns/uts the UTS namespace /proc/pid/ns/ipc the IPC namespace /proc/pid/ns/net the network namespace /proc/pid/ns/pid the PID namespace /proc/pid/root the root directory /proc/pid/cwd the working directory respectively -m, --mount [file] Enter the mount namespace. If no file is specified enter the mount namespace of the target process. If file is specified enter the mount namespace specified by file. -u, --uts [file] Enter the UTS namespace. If no file is specified enter the UTS namespace of the target process. If file is specified enter the UTS namespace specified by file. -i, --ipc [file] Enter the IPC namespace. If no file is specified enter the IPC namespace of the target process. If file is specified enter the IPC namespace specified by file. -n, --net [file] Enter the network namespace. If no file is specified enter the network namespace of the target process. If file is specified enter the network namespace specified by file. -p, --pid [file] Enter the PID namespace. If no file is specified enter the PID namespace of the target process. If file is specified enter the PID namespace specified by file. -r, --root [directory] Set the root directory. If no directory is specified set the root directory to the root directory of the target process. If direc- tory is specified set the root directory to the specified directory. -w, --wd [directory] Set the working directory. If no directory is specified set the working directory to the working directory of the target process. If directory is specified set the working directory to the specified directory. -F, --no-fork Do not fork before exec'ing the specified program. By default when entering a pid namespace enter calls fork before calling exec so that the children will be in the newly entered pid namespace. -V, --version Display version information and exit. -h, --help Print a help message. SEE ALSO
setns(2), clone(2) AUTHOR
Eric Biederman <ebiederm@xmission.com> AVAILABILITY
The nsenter command is part of the util-linux package and is available from Linux Kernel Archive <ftp://ftp.kernel.org/pub/linux/utils /util-linux/>. util-linux January 2013 NSENTER(1)
All times are GMT -4. The time now is 02:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy