Not a user of this, but this port is now obviously broken after dhclient removal. `dhclient ifN` has already been `ifconfig ifN inet autoconf' for years, so do that.
Neither blocks or guarantees that we actually get an IP, but that's apparently hasn't been a problemm in so far as noone bothered to patch/fix this port. Is anyone actually using this? Index: Makefile =================================================================== RCS file: /cvs/ports/security/vpnc/Makefile,v diff -u -p -r1.29 Makefile --- Makefile 27 Sep 2023 16:34:38 -0000 1.29 +++ Makefile 6 Jul 2024 08:38:32 -0000 @@ -1,7 +1,7 @@ COMMENT= client for Cisco 3000 VPN concentrators DISTNAME= vpnc-0.5.3 -REVISION= 6 +REVISION= 7 CATEGORIES= security net HOMEPAGE= http://www.unix-ag.uni-kl.de/~massar/vpnc/ Index: files/vpnc.sh =================================================================== RCS file: /cvs/ports/security/vpnc/files/vpnc.sh,v diff -u -p -r1.5 vpnc.sh --- files/vpnc.sh 11 Mar 2022 19:54:08 -0000 1.5 +++ files/vpnc.sh 11 Jul 2024 17:12:16 -0000 @@ -6,7 +6,7 @@ VPNGATEWAY=192.168.0.1 case "$1" in start) - dhclient ${PHYS_IF} + ifconfig ${PHYS_IF} inet autoconf DEFAULTROUTER=`route -n show -inet | grep default | awk '{ print $2 }'` ${PREFIX}/sbin/vpnc || exit 1 TUN_IP=`ifconfig ${TUN_IF} | grep netmask | awk '{ print $2 }'` @@ -17,7 +17,7 @@ start) stop) route delete -host ${VPNGATEWAY} pkill vpnc - pkill "dhclient ${PHYS_IF}" + ifconfig ${PHYS_IF} inet -autoconf ifconfig ${PHYS_IF} down ;; *)
