10-29-2009
We know "/usr/bin/netstat -an -f inet" gives all the data but it has diffrent formats of displaying reports for TCP and UDP.
Its certainly a tricky need.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I need help in the form of the complete procedures necessary in setting up an Apache web server on a Sun Sparc running Solaris 8
David Johnston
P.S New to the Unix arena (1 Reply)
Discussion started by: David Johnston
1 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I currently have two processes running on my Solaris server that are hogging the cpu. I am confident that these two processes are caused by remote users logged into the oracle database on the server.
What I need to know is how to get the corresponding ip address associated with the... (2 Replies)
Discussion started by: gwhelan
2 Replies
3. Solaris
SOLUTION:
You'll want to download the Solaris patches from: http://sunsolve.sun.com/show.do?target=home - get yourself an account, and you'll want to at least download the 'Sun Alert Patch Cluster' for your OS, as well as the 'Recommended' patch archive, which usually has a generic title like... (2 Replies)
Discussion started by: b1f30
2 Replies
4. Solaris
Can anyone explain me what is the use of zones in solaris. Also how to find whether it is a local or global zone. (1 Reply)
Discussion started by: rogerben
1 Replies
5. Solaris
Hi,
can anyone help in finding the hardware related details of I/O devices of remote solaris machine .Thanks in advance. (7 Replies)
Discussion started by: pratheepv
7 Replies
6. Solaris
Hi,
I need the following information.
1. We have raw disks but how to identify raw disks. Is there any command to identify its type and size.
2. How to differentiate between disks which are used as file system and that are still available to be used as raw. I know we can use df -n to... (7 Replies)
Discussion started by: malikshahid85
7 Replies
7. Solaris
how do you get start and end sector of a UFS slice? (2 Replies)
Discussion started by: orange47
2 Replies
8. UNIX for Advanced & Expert Users
Hi,
I'm trying to figure out how much traffic has been generated and received from netstat -s output (using Linux). I can see the output shows packet counts and Octet values, how would I correctly calculate how much traffic in and how much out?
My output below:
Ip:
88847576 total... (1 Reply)
Discussion started by: wilsonee
1 Replies
9. OS X (Apple)
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. Solaris
Greetings!
After block level migration using an external appliance, the luns are getting reported as DGC-RAID5 and these luns are infact from the new storage. I have a query on changing the device Vendor info from DGC-RAID5 to HP3par in the format o/p only.
AVAILABLE DISK SELECTIONS:
... (3 Replies)
Discussion started by: n_Bhaskar
3 Replies
LEARN ABOUT DEBIAN
blackhole
BLACKHOLE(4) BSD Kernel Interfaces Manual BLACKHOLE(4)
NAME
blackhole -- a sysctl(8) MIB for manipulating behaviour in respect of refused TCP or UDP connection attempts
SYNOPSIS
sysctl net.inet.tcp.blackhole[=[0 | 1 | 2]]
sysctl net.inet.udp.blackhole[=[0 | 1]]
DESCRIPTION
The blackhole sysctl(8) MIB is used to control system behaviour when connection requests are received on TCP or UDP ports where there is no
socket listening.
Normal behaviour, when a TCP SYN segment is received on a port where there is no socket accepting connections, is for the system to return a
RST segment, and drop the connection. The connecting system will see this as a ``Connection refused''. By setting the TCP blackhole MIB to
a numeric value of one, the incoming SYN segment is merely dropped, and no RST is sent, making the system appear as a blackhole. By setting
the MIB value to two, any segment arriving on a closed port is dropped without returning a RST. This provides some degree of protection
against stealth port scans.
In the UDP instance, enabling blackhole behaviour turns off the sending of an ICMP port unreachable message in response to a UDP datagram
which arrives on a port where there is no socket listening. It must be noted that this behaviour will prevent remote systems from running
traceroute(8) to a system.
The blackhole behaviour is useful to slow down anyone who is port scanning a system, attempting to detect vulnerable services on a system.
It could potentially also slow down someone who is attempting a denial of service attack.
WARNING
The TCP and UDP blackhole features should not be regarded as a replacement for firewall solutions. Better security would consist of the
blackhole sysctl(8) MIB used in conjuction with one of the available firewall packages.
This mechanism is not a substitute for securing a system. It should be used together with other security mechanisms.
SEE ALSO
ip(4), tcp(4), udp(4), ipf(8), ipfw(8), pfctl(8), sysctl(8)
HISTORY
The TCP and UDP blackhole MIBs first appeared in FreeBSD 4.0.
AUTHORS
Geoffrey M. Rehmet
BSD
January 1, 2007 BSD