04-18-2011
Perhaps someone can help mr to under this lsof output
When the maximum connection 10 error occur I tried
$ lsof -i | grep 2773156
AppServ 2773156 apuser 263u IPv6 0xf100060005936398 0t0 TCP *:7780 (LISTEN)
:
AppServ 2773156 apuser 283u IPv6 0xf100060004feca90 0t0 TCP dev1.cs.ata:*->10.126.73.4:45366
AppServ 2773156 apuser 288u IPv6 0xf10006000287d290 0t0 TCP dev1.cs.ata:*->10.126.73.4:45936
:
AppServ 2773156 apuser 323u IPv4 0xf100060005563b98 0t0 TCP dev1.cs.ata:53553->dev2.cs.ctc:25550 (ESTABLISHED)
Where 2773156 is the application process and it is listening on 7780
I saw the 7780 listener and 9 of
AppServ 2773156 apuser 283u IPv6 0xf100060004feca90 0t0 TCP dev1.cs.ata:*->10.126.73.4:45366
I think this represents 9 connections. But it does not say what port. Instead it has :*.
What does :* means ? If this are connections, why there is no status (such as ESTABLISHED) like the one coming from dev2.cs.ctc:25550 ?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
# netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
net1 1500 192.168 192.168.0.11 24508 0 12212 112931 2795
lo0 8232 127 127.0.0.1 42 0 42 0 0
atl0* 8232 none none No Statistics... (1 Reply)
Discussion started by: samprax
1 Replies
2. Shell Programming and Scripting
i'd like to grep a range of ports on a netstat -nt output, localaddress, say :1 to :1023. how do i do it via sed/awk/grep?
Thanks,
Marc (1 Reply)
Discussion started by: marcpascual
1 Replies
3. Solaris
Dear Experts,
I put below command-
could you please describe the outputs column-
let me describe some them-
col_1: (10.131.60.48.55880) The IP address of the local computer and the port number being used for this particular connection appear in the Local Address column.
col_2:... (3 Replies)
Discussion started by: thepurple
3 Replies
4. HP-UX
Hi,
Does anyone know why I get a different output when using "netstat -a" or "netstat -an" ??
# netstat -a | grep ts15r135
tcp 0 0 nbsol152.62736 ts15r135.23211 ESTABLISHED
# netstat -an | grep 172.23.160.78
tcp 0 0 135.246.39.152.51954 ... (4 Replies)
Discussion started by: ejdv
4 Replies
5. UNIX for Dummies Questions & Answers
hi all,
when I run-
wcars1j5#netstat -an | grep 8090
127.0.0.1.8090 *.* 0 0 49152 0 LISTEN
wcars1j5#
1. does this mean that no one is connected to this port?
Regards,
akash (1 Reply)
Discussion started by: akash_mahakode
1 Replies
6. IP Networking
I can't tell what the output of the netstat command means. Is there anywhere that has this information? I tried the man pages, but they weren't helpful. (3 Replies)
Discussion started by: Ultrix
3 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have old SCO O/S. System keeps crashing. I made lot of changes to kernel but so for nothing helped. I wrote a script which takes netstat -an output every one minute. I saw some thing right before the system crashed. Not sure if this means anything..
uname -a
SCO_SV djx2 3.2... (2 Replies)
Discussion started by: samnyc
2 Replies
8. IP Networking
Hello
netstat -p give below 6634176 connections as closed.How do we trace that which all connections are being closed on the server?
1366888371 data packet headers correctly predicted
1195906 connection requests
5227320 connection accepts
5992919... (6 Replies)
Discussion started by: Vishal_dba
6 Replies
9. Shell Programming and Scripting
Hi Team,
Below is the output of netstat -an | grep 1533
tcp 0 0 17.18.18.12:583 10.3.2.0:1533 ESTABLISHED
tcp 0 0 17.18.18.12:370 10.3.2.0:1533 ESTABLISHED
Below is the o/p of netstat -a | grep server_name
tcp 0 ... (4 Replies)
Discussion started by: Girish19
4 Replies
10. UNIX for Beginners Questions & Answers
Hi All,
I am trying to collect the listen ports info from netstat command in centos 7
From that info i am trying to collect all the foreign address IP for those ports.
I am using below script to do the same.
netstat -an |grep -w "LISTEN" |grep -v "127.0.0.1" |awk '{print $4}' >... (3 Replies)
Discussion started by: sravani25
3 Replies
FAITH(4) BSD Kernel Interfaces Manual FAITH(4)
NAME
faith -- IPv6-to-IPv4 TCP relay capturing interface
SYNOPSIS
device faith
DESCRIPTION
The faith interface captures IPv6 TCP traffic, for implementing userland IPv6-to-IPv4 TCP relay like faithd(8).
Each faith interface is created at runtime using interface cloning. This is most easily done with the ifconfig(8) create command or using
the cloned_interfaces variable in rc.conf(5).
Special action will be taken when IPv6 TCP traffic is seen on a router, and the routing table suggests to route it to the faith interface.
In this case, the packet will be accepted by the router, regardless of the list of IPv6 interface addresses assigned to the router. The
packet will be captured by an IPv6 TCP socket, if it has the IN6P_FAITH flag turned on and matching address/port pairs. As a result, faith
will let you capture IPv6 TCP traffic to some specific destination addresses. Userland programs, such as faithd(8) can use this behavior to
relay IPv6 TCP traffic to IPv4 TCP traffic. The program can accept some specific IPv6 TCP traffic, perform getsockname(2) to get the IPv6
destination address specified by the client, and perform application-specific address mapping to relay IPv6 TCP to IPv4 TCP.
The IN6P_FAITH flag on a IPv6 TCP socket can be set by using setsockopt(2), with level IPPROTO_IPV6 and optname IPv6_FAITH.
To handle error reports by ICMPv6, some ICMPv6 packets routed to an faith interface will be delivered to IPv6 TCP, as well.
To understand how faith can be used, take a look at the source code of faithd(8).
As the faith interface implements potentially dangerous operations, great care must be taken when configuring it. To avoid possible misuse,
the sysctl(8) variable net.inet6.ip6.keepfaith must be set to 1 prior to using the interface. When net.inet6.ip6.keepfaith is 0, no packets
will be captured by the faith interface.
The faith interface is intended to be used on routers, not on hosts.
SEE ALSO
inet(4), inet6(4), faithd(8)
Jun-ichiro itojun Hagino and Kazu Yamamoto, An IPv6-to-IPv4 transport relay translator, RFC3142.
HISTORY
The FAITH IPv6-to-IPv4 TCP relay translator first appeared in the WIDE hydrangea IPv6 stack.
BSD
April 10, 1999 BSD