From owner-freebsd-current@FreeBSD.ORG Mon Jan 25 15:54:56 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C4451065676; Mon, 25 Jan 2010 15:54:56 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id D0C1C8FC19; Mon, 25 Jan 2010 15:54:55 +0000 (UTC) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id o0PFssqd012115; Mon, 25 Jan 2010 07:54:55 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 25 Jan 2010 07:52:56 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: tun setup (routing?) issue in head Thread-Index: AcqdvJcHBYXgJd9IRSK9UrbZhv7sPQAGd89+ References: <4B5D92C7.8070908@icyb.net.ua> From: "Li, Qing" To: "Andriy Gapon" , , Cc: Subject: RE: tun setup (routing?) issue in head X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2010 15:54:56 -0000 Yes, the failure is due to route installation. To make a long story = short, many of the scripts that worked before not necessary because of the right reasons.=20 =20 I have been very busy at work, but I do have a patch and I will try to = get it=20 finalized shortly. =20 -- Qing =20 ________________________________ From: owner-freebsd-current@freebsd.org on behalf of Andriy Gapon Sent: Mon 1/25/2010 4:47 AM To: freebsd-net@freebsd.org; freebsd-current@freebsd.org Subject: tun setup (routing?) issue in head I've updated my HEAD amd64 system from December's sources to something = more recent and I've got problems with security/vpnc. To be precise vpnc itself = seems to work as good as before but its post-connect script is now failing: $ ifconfig tun0 inet 10.99.15.144 10.99.15.144 netmask 255.255.255.255 = mtu 1412 up ifconfig: ioctl (SIOCAIFADDR): File exists Where tun0 is an interface created by vpnc. ktrace gives this: ifconfig CALL socket(PF_INET,SOCK_DGRAM,IPPROTO_IP) ifconfig RET socket 3 ifconfig CALL ioctl(0x3,SIOCSIFMTU,0x525a60) ifconfig RET ioctl 0 ifconfig CALL ioctl(0x3,SIOCGIFFLAGS,0x7fffffffda30) ifconfig RET ioctl 0 ifconfig CALL ioctl(0x3,SIOCSIFFLAGS,0x7fffffffda30) ifconfig RET ioctl 0 ifconfig CALL ioctl(0x3,SIOCDIFADDR,0x525380) ifconfig RET ioctl -1 errno 49 Can't assign requested address ifconfig CALL ioctl(0x3,SIOCAIFADDR,0x525340) ifconfig RET ioctl -1 errno 17 File exists ifconfig CALL write(0x2,0x7fffffffd2d0,0xa) So, what's happening? Do you I have to update the ifconfig command? Or is there some issue in the networking code? BTW, I also get the following messages in the system log when vpnc is = started: kernel: tun0: link state changed to UP kernel: ifa_add_loopback_route: insertion failed I have net.link.tap.up_on_open=3D1 in sysctl.conf if that matters. -- Andriy Gapon _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org"