Sponsored Content
Special Forums IP Networking netstat -i always shows Idrop 48665 Post 302978910 by drhowarddrfine on Friday 5th of August 2016 11:41:21 AM
Old 08-05-2016
netstat -i always shows Idrop 48665

I made some minor changes to my nginx server using a Linux VPS running FreeBSD 10.3 with TLS, ciphers and then file caches. Except for the file caching, I had done these changes before without issue. I went away for the weekend and, when I came back, netstat -i showed Idrop as being 48665. The web sites on this server don't exhibit any problems that I can see.

I reverted all my changes back to their original but I still see the same value for Idrop and it never changes from day to day or throughout the day. All the other values change accordingly.

Code:
Name    Mtu Network       Address              Ipkts Ierrs Idrop    Opkts Oerrs  Coll
em0    1500 <Link#1>      xx:xx:3c:cd:7e:c7 725249751     0 48665  2735394     0     0
em0       - xxxx::xxx:3cf xxxx::xxx:3cff:fe        0     -     -        3     -     -
em0       - xxx.xxx.21.23 website2.co      268     -     -        0     -     -
em0       - xxx.xxx.21.0  website3.or     1128     -     -     1221     -     -
lo0   16384 <Link#2>                            2227     0     0     2227     0     0
lo0       - ::1           ::1                      0     -     -        0     -     -
lo0       - xxxx::1%lo0   xxxx::1%lo0              0     -     -        0     -     -
lo0       - your-net      localhost                0     -     -        0     -     -

Notice that there are two web sites shown, both on different IPs. However, there are two other web sites on this same server with the same IP as website2 but they aren't listed. What's with that?

I have to say that, while I love networking, I never get to deal with it and this server has been around for several years, running without issues, so I'm at a loss as to how to troubleshoot this.


Moderator's Comments:
Mod Comment Please use CODE tags as required by forum rules!

Last edited by RudiC; 08-05-2016 at 01:35 PM.. Reason: Changed ICODE to CODE tags.
 

10 More Discussions You Might Find Interesting

1. IP Networking

Netstat

Giving netstat command on the prompt gives commands such as localhost.43592 localhost.35237 32768 0 32768 0 TIME_WAIT localhost.43594 localhost.43595 32768 0 32768 0 TIME_WAIT localhost.43598 localhost.35237 32768 0 32768 0 TIME_WAIT... (6 Replies)
Discussion started by: DPAI
6 Replies

2. IP Networking

netstat

Hi what is the command to see the process name/application name along with the port number, connection status ... netstat is not giving process/application name Is there any way to know which application is holding which port? Thanks in advance (3 Replies)
Discussion started by: axes
3 Replies

3. UNIX for Dummies Questions & Answers

netstat not working

Hello, One of the solaris machine in our network is giving an error when the netstat command is executed. soloman:/home/db2admin->netstat ip open: Permission denied can't open mib stream: Bad file number But it works with root. I couldnt' get any useful info during my search in google. ... (2 Replies)
Discussion started by: k_pranava
2 Replies

4. UNIX for Advanced & Expert Users

Netstat command

Hi.., Now, I am reading about the netstat command and its implementation. I have doubts in some options and its functionalities, natstat - M (Which is described as display masqueraded connections), what it means? What is Forwarding Information Base.?(--fib) Thanks in advance,... (3 Replies)
Discussion started by: nagalenoj
3 Replies

5. Solaris

netstat -- what am i looking at?

Greetings to all, Here is a line of output from my netstat command cbp031.904 wdcprodhome.nfsd 98304 0 49640 0 ESTABLISHED The only thing i recognize is the unix machine "cbp031" but what is .904 and all the other data telling me? Thanks in advance. (3 Replies)
Discussion started by: Harleyrci
3 Replies

6. Shell Programming and Scripting

netstat command

Hi, In my project we use sftp with batch mode (password less) script in parallel for 14 sessions which connects to 2 different servers alternatively i.e. 7 connects to one server say server1 and the other 7 connects to say server 2. Now the problem is that these 14 sessions are run in... (5 Replies)
Discussion started by: dips_ag
5 Replies

7. UNIX for Advanced & Expert Users

Help with netstat

Hi, I want to list the time for how long a secure connections last to my server/blade. i am using netstat command to get the same, but not sure how to get the time for how long connections is being ESTABLISHED. netstat -na | grep 'ESTABLISHED' | grep :443 |awk '{print $4}' | cut -d: -f1 |... (1 Reply)
Discussion started by: Siddheshk
1 Replies

8. Red Hat

netstat

Hi Can any body tell me about TIME_WAIT status meaning in the following command output. # netstat -anp|grep 5000 tcp 0 0 127.0.0.1:50006 0.0.0.0:* LISTEN 5058/ccsd tcp 0 0 0.0.0.0:50008 0.0.0.0:* ... (3 Replies)
Discussion started by: mastansaheb
3 Replies

9. OS X (Apple)

netstat

When running netstat -i from the Command Terminal, It returns with 21 different connections.. The addresses all look like this: ::1 fe80:1::1 10:dd:b1:a5:c4:ba with Network names like Linke#2 fe80::8e2d How can I delve deeper into this to clarify what is going on with my network?... (0 Replies)
Discussion started by: dwfiedler
0 Replies

10. Shell Programming and Scripting

netstat output

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
routing(7)						 Miscellaneous Information Manual						routing(7)

NAME
routing - system support for local network packet routing DESCRIPTION
The network facilities for HP-UX provide general packet routing support. Routing table maintenance is handled by application processes. A routing table consists of a set of data structures used by the network facilities to select the appropriate remote host or gateway when transmitting packets. The table contains a single entry for each route to a specific network or host, as displayed by the command with the or options (see netstat(1)). Routes that are not valid are not displayed. _______________________________________________________________ # netstat -r Routing tables Destination Gateway Flags Refs Use Interface Pmtu hpindwr.cup.hp.com localhost UH 1 39 lo0 4608 localhost localhost UH 0 68 lo0 4608 147.253.56.195 localhost UH 0 0 lo0 4608 147.253.144.66 localhost UH 0 0 lo0 4608 default hpinsmh.cup.hp.com UG 1 21 lan0 1500 15.13.136 hpindwr.cup.hp.com U 1 92 lan0 1500 147.253.56 147.253.56.195 U 0 7 lan2 1500 147.253.144.64 147.253.144.66 U 0 7 lan1 1500 _______________________________________________________________ # netstat -rn Routing tables Destination Gateway Flags Refs Use Interface Pmtu 15.13.136.66 127.0.0.1 UH 1 39 lo0 4608 127.0.0.1 127.0.0.1 UH 0 68 lo0 4608 147.253.56.195 127.0.0.1 UH 0 0 lo0 4608 147.253.144.66 127.0.0.1 UH 0 0 lo0 4608 default 15.13.136.11 UG 2 30 lan0 1500 15.13.136.0 15.13.136.66 U 1 113 lan0 1500 147.253.56.0 147.253.56.195 U 0 7 lan2 1500 147.253.144.64 147.253.144.66 U 0 7 lan1 1500 _______________________________________________________________ # netstat -rv Routing tables Dest/Netmask Gateway Flags Refs Use Interface Pmtu hpindwr.cup.hp.com/0xffffffff localhost UH 1 39 lo0 4608 localhost/0xffffffff localhost UH 0 68 lo0 4608 147.253.56.195/0xffffffff localhost UH 0 0 lo0 4608 147.253.144.66/0xffffffff localhost UH 0 0 lo0 4608 default/0x00000000 hpinsmh.cup.hp.com UG 2 31 lan0 1500 15.13.136/0xfffff800 hpindwr.cup.hp.com U 1 129 lan0 1500 147.253.56/0xfffffe00 147.253.56.195 U 0 7 lan2 1500 147.253.144.64/0xfffffff0 147.253.144.66 U 0 7 lan1 1500 _______________________________________________________________ # netstat -rnv Routing tables Dest/Netmask Gateway Flags Refs Use Interface Pmtu 15.13.136.66/255.255.255.255 127.0.0.1 UH 1 39 lo0 4608 127.0.0.1/255.255.255.255 127.0.0.1 UH 0 68 lo0 4608 147.253.56.195/255.255.255.255 127.0.0.1 UH 0 0 lo0 4608 147.253.144.66/255.255.255.255 127.0.0.1 UH 0 0 lo0 4608 default/0.0.0.0 15.13.136.11 UG 3 40 lan0 1500 15.13.136.0/255.255.248.0 15.13.136.66 U 1 153 lan0 1500 147.253.56.0/255.255.254.0 147.253.56.195 U 0 8 lan2 1500 147.253.144.64/255.255.255.240 147.253.144.66 U 0 8 lan1 1500 _______________________________________________________________ The following columns are of particular interest: The destination Internet address: host name, network name, or The keyword indicates a wildcard route, used as a last resort if no route is specified for a particular remote host or network. See The netmask and the destination Internet address together define a range of IP addresses that may be reached by the route's gateway. A host route by default has a netmask of all 1's. A default route by default has a netmask of all 0's. The netmask is also used in selecting a route to forward an IP packet. See the subsection. The gateway to use to get to the destination: a remote gateway or the local host. See The type of route: The route is "up" or available (see ifconfig(1M)). The route uses a remote host as a gateway; otherwise, the local host is shown as the gateway (see route(1M)). The destination is a host; otherwise, the destination is a network (see route(1M)). The interface connections: The local loopback after system boot. The interface cards installed on the local host after the command is executed at boot time (see ifconfig(1M)). The values of the count and destination type fields in the command determine the presence of the and flags in the display and thus the route type, as shown in the following table. Count Destination Type Flags Route Type ------------------------------------------------------------- =0 network U Route to a network directly from the local host >0 network UG Route to a network through a remote host gateway =0 host UH Route to a remote host directly from the local host >0 host UGH Route to a remote host through a remote host gateway =0 default U Wildcard route directly from the local host >0 default UG Wildcard route through a remote host gateway ------------------------------------------------------------- Subnets The network facilities support variable-length subnetting. An Internet address is made up of a portion, and a portion of an address in the form: Subnet addresses are defined as a portion of the network's Internet address. This scheme provides for: o Network addresses that identify physically distinct networks. o Subnet addresses that identify physically distinct subnetworks of the same network. A network manager can subdivide the Internet address of the local network into subnets using the host number space. This facility allows several physical networks to share a single Internet address. To allow for this, three Internet classes are defined, each accommodating a different amount of network and host addresses. The address classes are defined by the most significant bit of the binary form of the address. The following table lists the number of networks, nodes, and the address ranges for each address class: Nodes per Class Networks Network Address Range -------------------------------------------------------------- A 127 16777215 0.0.0.1 - 127.225.225.254 B 16383 65535 128.0.0.1 - 191.255.255.254 C 2097151 255 192.0.0.1 - 223.244.244.243 Reserved -- -- 224.0.0.0 - 255.255.255.255 -------------------------------------------------------------- The first 8 bits of a Class A network has network space for only 127, while accommodating the largest number of nodes possible among the classes defined. A single class B network has the network address limitation of 16 bits, and 16 bits to define the nodes. For example, a Class C address space is as follows: ______________________________________ Indicates Class C Class C subnet networks portion | | --- --- 10000000.00000110.00000001.11100001 -------------------------- ----- | | Network Address Host = 192.6.1 Address = 1 ______________________________________ A subnet for a given host is specified with the command (see ifconfig(1M)), using the parameter with a 32-bit subnet mask. The default masks for the three classes of Internet addresses are as follows: Class A: 255.0.0.0 Class B: 255.255.0.0 Class C: 255.255.255.0 An example Class C network number is 192.34.17.0. The last field specifies the host number. Thus, all hosts with the prefix 192.34.17 are recognized as being on the same logical and physical network. If subnets are not in use, the default mask used is 255.255.255.0. If subnets are used and the 8-bit host field is partitioned into 3 bits of subnet and 5 bits of host as in the above example, then the sub- net mask would be 255.255.255.192. If a host has multiple interfaces, then it can belong to different subnets. Unlike past releases, the subnets can have different sizes even if they may have the same network address. This is accomplished by using a different netmask on each of the host interfaces. For example, the and interface shown in the tables above are connected to two distinct subnets of the same network, 147.253. The subnet that belongs to can have at most 14 hosts, because its netmask is 255.255.255.240. Note: The host portion of those IP addresses in the subnet cannot be all 1's or all 0's, therefore this subnet can support only 14 hosts, not 16. The subnet that belongs to can have up to 510 hosts, because its netmask is 255.255.254.0. Supernets A supernet is a collection of smaller networks. Supernetting is a technique of using the netmask to aggregate a collection of smaller net- works into a supernet. This technique is particularly useful for class C networks. A Class C network can only have 254 hosts. This can be too restrictive for some companies. For these companies, a netmask that only contains a portion of the network part can be applied to the hosts in these class C networks to form a supernet. This supernet netmask should be applied to those interfaces that connect to the supernet using the ifconfig command (see ifconfig(1M)). For example, a host can configure its interface to connect to a class C supernet, for example, 192.6, by configuring an IP address of 192.6.1.1 and a netmask of 255.255.0.0 to its interface. Routing Algorithm The routing table entries are of three types: o Entries for a specific host. o Entries for all hosts on a specific network. o Wildcard entries for any destination not matched by entries of the first two types. To select a route for forwarding an IP packet, the network facilities select the complete set of "matching" routing table entries from the routing table. A routing table entry is considered a match, if the result of the bit-wise AND operation between the netmask in the routing entry and the IP packet's destination address equals the destination address in the routing entry. The network facilities then select from the set the routing entries that have the longest netmask. The length of a netmask is defined as the number of contiguous 1 bits starting from the leftmost bit position in the 32-bit netmask field. In other words, the network facili- ties select the routing entry that specifies the narrowest range of IP addresses. For example, the host route entry that has a destina- tion/netmask pair of (147.253.56.1, 0xFFFFFFFF), is more specific than the network route entry that has a destination/netmask pair of (147.253.56.0, 0xFFFFFE00); therefore, the network facilities select the host route entry. The default route by default has a destina- tion/netmask pair of (0,0). Therefore, the default route matches all destinations but it is also the least specific. The default route will be selected only if there is not a more specific route. There may still be multiple routing entries remaining. In that case, the IP packet is routed over the first entry displayed by Such multi- ple routes include: o Two or more routes to a host via different gateways. o Two or more routes to a network via different gateways. A superuser can change entries in the table by using the command (see route(1M), or by information received in Internet Control Message Protocol (ICMP) redirect messages. If there are more than one default gateways for a particular net or subnet, each will be used in turn to effect the even distribution of datagrams to the different gateways. WARNINGS
Reciprocal commands must be executed on the local host and the destination host, as well as all intermediate hosts, if routing is to suc- ceed in the cases of virtual circuit connections or bidirectional datagram transfers. AUTHOR
was developed by the University of California, Berkeley. FILES
SEE ALSO
netstat(1), ifconfig(1M), route(1M), route(7P). routing(7)
All times are GMT -4. The time now is 11:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy