cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
112339c1d4
openbsd-ports/net/tcptraceroute/Makefile

38 lines
931 B
Makefile
Raw Normal View History

Install examples in share/examples, not share/doc. From Sebastian Stark; ok'ed by maintainer Patroklos G. Argyroudis
2002-12-23 20:08:43 -05:00
# $OpenBSD: Makefile,v 1.9 2002/12/24 01:08:43 pvalchev Exp $
tcptraceroute-1.2 import The more traditional traceroute(8) sends out either UDP or ICMP ECHO packets with a TTL of one, and increments the TTL until the destination has been reached. By printing the gateways that generate ICMP time exceeded messages along the way, it is able to determine the path packets are taking to reach the destination. The problem is that with the widespread use of firewalls on the modern Internet, many of the packets that traceroute(8) sends out end up being filtered, making it impossible to completely trace the path to the destination. However, in many cases, these firewalls will permit inbound TCP packets to specific ports that hosts sitting behind the firewall are listening for connections on. By sending out TCP SYN packets instead of UDP or ICMP ECHO packets, tcptraceroute is able to bypass the most common firewall filters.
2001-08-06 23:14:39 -04:00
COMMENT= "traceroute implementation using TCP packets"
Update to tcptraceroute-1.4; from maintainer Patroklos Argyroudis
2002-07-31 13:14:30 -04:00
DISTNAME= tcptraceroute-1.4
Install examples in share/examples, not share/doc. From Sebastian Stark; ok'ed by maintainer Patroklos G. Argyroudis
2002-12-23 20:08:43 -05:00
PKGNAME= ${DISTNAME}p1
tcptraceroute-1.2 import The more traditional traceroute(8) sends out either UDP or ICMP ECHO packets with a TTL of one, and increments the TTL until the destination has been reached. By printing the gateways that generate ICMP time exceeded messages along the way, it is able to determine the path packets are taking to reach the destination. The problem is that with the widespread use of firewalls on the modern Internet, many of the packets that traceroute(8) sends out end up being filtered, making it impossible to completely trace the path to the destination. However, in many cases, these firewalls will permit inbound TCP packets to specific ports that hosts sitting behind the firewall are listening for connections on. By sending out TCP SYN packets instead of UDP or ICMP ECHO packets, tcptraceroute is able to bypass the most common firewall filters.
2001-08-06 23:14:39 -04:00
CATEGORIES= net
HOMEPAGE= http://michael.toren.net/code/tcptraceroute/
uniformize maintainer addresses.
2002-05-10 20:31:22 -04:00
MAINTAINER= Patroklos Argyroudis <argp@ieee.org>
tcptraceroute-1.2 import The more traditional traceroute(8) sends out either UDP or ICMP ECHO packets with a TTL of one, and increments the TTL until the destination has been reached. By printing the gateways that generate ICMP time exceeded messages along the way, it is able to determine the path packets are taking to reach the destination. The problem is that with the widespread use of firewalls on the modern Internet, many of the packets that traceroute(8) sends out end up being filtered, making it impossible to completely trace the path to the destination. However, in many cases, these firewalls will permit inbound TCP packets to specific ports that hosts sitting behind the firewall are listening for connections on. By sending out TCP SYN packets instead of UDP or ICMP ECHO packets, tcptraceroute is able to bypass the most common firewall filters.
2001-08-06 23:14:39 -04:00
# GPL
PERMIT_PACKAGE_CDROM= Yes
PERMIT_PACKAGE_FTP= Yes
PERMIT_DISTFILES_CDROM= Yes
PERMIT_DISTFILES_FTP= Yes
MASTER_SITES= http://michael.toren.net/code/tcptraceroute/
LIB_DEPENDS= net::net/libnet
fix for 2.9-stable (naddy@) - sorry Patroklos, didn't see your port before import.
2001-08-09 21:09:36 -04:00
MAKE_FLAGS= CC="${CC}" \
Update to tcptraceroute-1.4; from maintainer Patroklos Argyroudis
2002-07-31 13:14:30 -04:00
CFLAGS="${CFLAGS} -L${LOCALBASE}/lib \
-I${LOCALBASE}/include"
fix for 2.9-stable (naddy@) - sorry Patroklos, didn't see your port before import.
2001-08-09 21:09:36 -04:00
ALL_TARGET=
No regression tests available.
2002-10-27 20:38:44 -05:00
NO_REGRESS= Yes
tcptraceroute-1.2 import The more traditional traceroute(8) sends out either UDP or ICMP ECHO packets with a TTL of one, and increments the TTL until the destination has been reached. By printing the gateways that generate ICMP time exceeded messages along the way, it is able to determine the path packets are taking to reach the destination. The problem is that with the widespread use of firewalls on the modern Internet, many of the packets that traceroute(8) sends out end up being filtered, making it impossible to completely trace the path to the destination. However, in many cases, these firewalls will permit inbound TCP packets to specific ports that hosts sitting behind the firewall are listening for connections on. By sending out TCP SYN packets instead of UDP or ICMP ECHO packets, tcptraceroute is able to bypass the most common firewall filters.
2001-08-06 23:14:39 -04:00
do-install:
oops bin->sbin noticed by valchev@
2001-08-07 00:23:22 -04:00
${INSTALL_PROGRAM} ${WRKSRC}/tcptraceroute ${PREFIX}/sbin
tcptraceroute-1.2 import The more traditional traceroute(8) sends out either UDP or ICMP ECHO packets with a TTL of one, and increments the TTL until the destination has been reached. By printing the gateways that generate ICMP time exceeded messages along the way, it is able to determine the path packets are taking to reach the destination. The problem is that with the widespread use of firewalls on the modern Internet, many of the packets that traceroute(8) sends out end up being filtered, making it impossible to completely trace the path to the destination. However, in many cases, these firewalls will permit inbound TCP packets to specific ports that hosts sitting behind the firewall are listening for connections on. By sending out TCP SYN packets instead of UDP or ICMP ECHO packets, tcptraceroute is able to bypass the most common firewall filters.
2001-08-06 23:14:39 -04:00
${INSTALL_DATA} ${WRKSRC}/tcptraceroute.8 ${PREFIX}/man/man8
Install examples in share/examples, not share/doc. From Sebastian Stark; ok'ed by maintainer Patroklos G. Argyroudis
2002-12-23 20:08:43 -05:00
${INSTALL_DATA_DIR} ${PREFIX}/share/examples/tcptraceroute
${INSTALL_DATA} ${WRKSRC}/examples.txt ${PREFIX}/share/examples/tcptraceroute
tcptraceroute-1.2 import The more traditional traceroute(8) sends out either UDP or ICMP ECHO packets with a TTL of one, and increments the TTL until the destination has been reached. By printing the gateways that generate ICMP time exceeded messages along the way, it is able to determine the path packets are taking to reach the destination. The problem is that with the widespread use of firewalls on the modern Internet, many of the packets that traceroute(8) sends out end up being filtered, making it impossible to completely trace the path to the destination. However, in many cases, these firewalls will permit inbound TCP packets to specific ports that hosts sitting behind the firewall are listening for connections on. By sending out TCP SYN packets instead of UDP or ICMP ECHO packets, tcptraceroute is able to bypass the most common firewall filters.
2001-08-06 23:14:39 -04:00
.include <bsd.port.mk>
Reference in New Issue Copy Permalink