01-07-2009
I suggest you use tcpdump from the AIX system to monitor network traffic to/fro the printer.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How do I use snoop command to capture multicast packets in the network? (1 Reply)
Discussion started by: caden312
1 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. AIX
So im fairly new to AIX and my knowledge is very, very limited but i got my hands on an RS6000 43P model and im trying to get it on the network so i can access it from work. I have pretty much tried everything i can/know how to do by reading up as much as i can but im still lost.
I have the 43P... (2 Replies)
Discussion started by: IIIII
2 Replies
4. UNIX for Dummies Questions & Answers
Hi,
My Solaris Workstation has got 4 NICS, out of which one of them(bge3) is unplugged from the rest of the external network & connected to other interface(bge1). The isolated NIC serves as a simulated Ethernet Interface for my application under development.
Now, I'd like to capture RAW... (1 Reply)
Discussion started by: smanu
1 Replies
5. UNIX for Dummies Questions & Answers
in a xen environment , i see a lot op dropped packets via netstat -i
Is this a sign of network problems, or is it normal to see this kind of numbers? i'm not sure how to interprete the data. is this normal, bad, critical. What are your stats on this?
I guess i have a xen issue of some sort,... (1 Reply)
Discussion started by: progressdll
1 Replies
6. Infrastructure Monitoring
Hi,
I want to capture snmp packets in AIX.
When i give print from AIX6.1, Printer will give its response thru' snmp.
I used iptrace command like below, but it is not capturing snmp packets other packets are captured like udp, tcp..
1. iptrace command:
/usr/sbin/iptrace -a -i en0... (1 Reply)
Discussion started by: meeraramanathan
1 Replies
7. IP Networking
Hi,
I want to capture a certain type of packets (selected according to the protocol) coming to my PC and then transmit them to another PC. I had the idea to use tcpdump to filter input packets and extract those chosen. Well my questions are:
1- after filtering input packets, those that have not... (1 Reply)
Discussion started by: ziedf
1 Replies
8. UNIX for Advanced & Expert Users
Hello folks,
Have a process which needs to lock files to prevent simultaneous access.
I could catch Ctrl + C, etc signals via the trap command.
Often sessions get hung due to network disconnect leaving the lock file in place.
Is there a way to catch network disconnects, etc.
Thanks in... (4 Replies)
Discussion started by: vibhor_agarwali
4 Replies
9. Programming
I have made an packet capture application running on intel machine, it is capturing packets with src address- 17.0.0.0 destination ip- 66.0.0.0, source port- 0, destination port- 0, and protocol- 0 what does these packets mean ?
The code written to interpreter captured bytes is given below.... (5 Replies)
Discussion started by: arunpushkar
5 Replies
10. Red Hat
I have three systems A,B,C. I want to configure A in such a way that all packets from A to C goes via B.
I tried:
1. ip route add 'ip of C' via 'ip of B'
2. route add -net 'net address' netmask gw 'ip of B'
These commands work initially when I try a ping or traceroute and expire after... (2 Replies)
Discussion started by: kanak
2 Replies
LEARN ABOUT DEBIAN
if_enc
ENC(4) BSD Kernel Interfaces Manual ENC(4)
NAME
enc -- Encapsulating Interface
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device enc
DESCRIPTION
The enc interface is a software loopback mechanism that allows hosts or firewalls to filter ipsec(4) traffic using any firewall package that
hooks in via the pfil(9) framework.
The enc interface allows an administrator to see incoming and outgoing packets before and after they will be or have been processed by
ipsec(4) via tcpdump(1).
The ``enc0'' interface inherits all IPsec traffic. Thus all IPsec traffic can be filtered based on ``enc0'', and all IPsec traffic could be
seen by invoking tcpdump(1) on the ``enc0'' interface.
What can be seen with tcpdump(1) and what will be passed on to the firewalls via the pfil(9) framework can be independently controlled using
the following sysctl(8) variables:
Name Defaults Suggested
net.enc.out.ipsec_bpf_mask 0x00000003 0x00000001
net.enc.out.ipsec_filter_mask 0x00000001 0x00000001
net.enc.in.ipsec_bpf_mask 0x00000001 0x00000002
net.enc.in.ipsec_filter_mask 0x00000001 0x00000002
For the incoming path a value of 0x1 means ``before stripping off the outer header'' and 0x2 means ``after stripping off the outer header''.
For the outgoing path 0x1 means ``with only the inner header'' and 0x2 means ``with outer and inner headers''.
incoming path |------|
---- IPsec processing ---- (before) ---- (after) ----> | |
| Host |
<--- IPsec processing ---- (after) ----- (before) ---- | |
outgoing path |------|
Most people will want to run with the suggested defaults for ipsec_filter_mask and rely on the security policy database for the outer head-
ers.
EXAMPLES
To see the packets the processed via ipsec(4), adjust the sysctl(8) variables according to your need and run:
tcpdump -i enc0
SEE ALSO
tcpdump(1), bpf(4), ipf(4), ipfw(4), ipsec(4), pf(4), tcpdump(8)
BSD
November 28, 2007 BSD