Date: Sat, 19 Dec 2009 12:59:51 GMT From: Chen Xing <chen@starworm.com> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/141773: net/iodine: iodined fails to properly setup the tun-device Message-ID: <200912191259.nBJCxpT1087436@www.freebsd.org> Resent-Message-ID: <200912191300.nBJD0HBJ057647@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 141773 >Category: ports >Synopsis: net/iodine: iodined fails to properly setup the tun-device >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Dec 19 13:00:17 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Chen Xing >Release: FreeBSD 8.0-RELEASE amd64 >Organization: >Environment: FreeBSD x.y.z 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: iodined fails to properly setup the tun-device opon execution. # iodined -P test 192.168.0.1 x.y.z Opened /dev/tun0 Setting IP of tun0 to 192.168.0.1 ifconfig: ioctl (SIOCAIFADDR): Destination address required Looking more closely, the tun.c patch attempts to fix the problem but fails to do so. Neither the patched nor the unpatched version work as a tun-device can neither be created without a destination adress (patched behavior) nor with the destination adress equal to source adress (unpatched behavior). >How-To-Repeat: # iodined -P test 192.168.0.1 x.y.z >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200912191259.nBJCxpT1087436>