| blackhole.4 (108506) | blackhole.4 (117011) |
|---|---|
| 1.\" 2.\" blackhole - drop refused TCP or UDP connects 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 13.\" | 1.\" 2.\" blackhole - drop refused TCP or UDP connects 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 13.\" |
| 14.\" $FreeBSD: head/share/man/man4/blackhole.4 108506 2002-12-31 16:29:15Z chris $ | 14.\" $FreeBSD: head/share/man/man4/blackhole.4 117011 2003-06-28 23:53:39Z ru $ |
| 15.Dd August 17, 1999 16.Dt BLACKHOLE 4 17.Os 18.Sh NAME 19.Nm blackhole 20.Nd a 21.Xr sysctl 8 22MIB for manipulating behaviour in respect of refused TCP or UDP connection --- 5 unchanged lines hidden (view full) --- 28The 29.Nm 30.Xr sysctl 8 31MIB is used to control system behaviour when connection requests 32are received on TCP or UDP ports where there is no socket listening. 33.Pp 34Normal behaviour, when a TCP SYN segment is received on a port where 35there is no socket accepting connections, is for the system to return | 15.Dd August 17, 1999 16.Dt BLACKHOLE 4 17.Os 18.Sh NAME 19.Nm blackhole 20.Nd a 21.Xr sysctl 8 22MIB for manipulating behaviour in respect of refused TCP or UDP connection --- 5 unchanged lines hidden (view full) --- 28The 29.Nm 30.Xr sysctl 8 31MIB is used to control system behaviour when connection requests 32are received on TCP or UDP ports where there is no socket listening. 33.Pp 34Normal behaviour, when a TCP SYN segment is received on a port where 35there is no socket accepting connections, is for the system to return |
| 36a RST segment, and drop the connection. The connecting system will 37see this as a "Connection refused". By setting the TCP blackhole | 36a RST segment, and drop the connection. 37The connecting system will 38see this as a 39.Dq Connection refused . 40By setting the TCP blackhole |
| 38MIB to a numeric value of one, the incoming SYN segment 39is merely dropped, and no RST is sent, making the system appear | 41MIB to a numeric value of one, the incoming SYN segment 42is merely dropped, and no RST is sent, making the system appear |
| 40as a blackhole. By setting the MIB value to two, any segment arriving 41on a closed port is dropped without returning a RST. This provides 42some degree of protection against stealth port scans. | 43as a blackhole. 44By setting the MIB value to two, any segment arriving 45on a closed port is dropped without returning a RST. 46This provides some degree of protection against stealth port scans. |
| 43.Pp 44In the UDP instance, enabling blackhole behaviour turns off the sending 45of an ICMP port unreachable message in response to a UDP datagram which | 47.Pp 48In the UDP instance, enabling blackhole behaviour turns off the sending 49of an ICMP port unreachable message in response to a UDP datagram which |
| 46arrives on a port where there is no socket listening. It must be noted 47that this behaviour will prevent remote systems from running | 50arrives on a port where there is no socket listening. 51It must be noted that this behaviour will prevent remote systems from running |
| 48.Xr traceroute 8 49to a system. 50.Pp 51The blackhole behaviour is useful to slow down anyone who is port scanning 52a system, attempting to detect vulnerable services on a system. 53It could potentially also slow down someone who is attempting a denial 54of service attack. 55.Sh WARNING 56The TCP and UDP blackhole features should not be regarded as a replacement 57for 58.Xr ipfw 8 | 52.Xr traceroute 8 53to a system. 54.Pp 55The blackhole behaviour is useful to slow down anyone who is port scanning 56a system, attempting to detect vulnerable services on a system. 57It could potentially also slow down someone who is attempting a denial 58of service attack. 59.Sh WARNING 60The TCP and UDP blackhole features should not be regarded as a replacement 61for 62.Xr ipfw 8 |
| 59as a tool for firewalling a system. In order to create a highly 60secure system, | 63as a tool for firewalling a system. 64In order to create a highly secure system, |
| 61.Xr ipfw 8 62should be used for protection, not the blackhole feature. 63.Pp 64This mechanism is not a substitute for securing a system. 65It should be used together with other security mechanisms. 66.Sh SEE ALSO 67.Xr ip 4 , 68.Xr tcp 4 , 69.Xr udp 4 , 70.Xr ipfw 8 , 71.Xr sysctl 8 72.Sh AUTHORS 73.An Geoffrey M. Rehmet 74.Sh HISTORY 75The TCP and UDP 76.Nm 77MIBs 78first appeared in 79.Fx 4.0 . | 65.Xr ipfw 8 66should be used for protection, not the blackhole feature. 67.Pp 68This mechanism is not a substitute for securing a system. 69It should be used together with other security mechanisms. 70.Sh SEE ALSO 71.Xr ip 4 , 72.Xr tcp 4 , 73.Xr udp 4 , 74.Xr ipfw 8 , 75.Xr sysctl 8 76.Sh AUTHORS 77.An Geoffrey M. Rehmet 78.Sh HISTORY 79The TCP and UDP 80.Nm 81MIBs 82first appeared in 83.Fx 4.0 . |