From owner-freebsd-net@FreeBSD.ORG Sat Jul 26 07:24:09 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1F3F434A for ; Sat, 26 Jul 2014 07:24:09 +0000 (UTC) Received: from mail.shmtech.biz (unknown [IPv6:2001:41c8:10:8c::4:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.shmtech.biz", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AE0E92F4A for ; Sat, 26 Jul 2014 07:24:08 +0000 (UTC) Received: from fleabag.domlan.talk2dom.com (92.40.4.124.threembb.co.uk [92.40.4.124]) (authenticated bits=0) by mail.shmtech.biz (8.14.8/8.14.5) with ESMTP id s6Q7O5aw059105 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Sat, 26 Jul 2014 08:24:06 +0100 (BST) (envelope-from dom@talk2dom.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=talk2dom.com; s=shmtech1; t=1406359446; bh=/p4wY/pbCcGIsFzcVDtLiVemG11qnmnz3P19SyKPtY0=; h=Date:From:To:Subject:References:In-Reply-To; b=loWUi0+gbrf0SulKFcOiYhcNjv9788UA2osUKm3UWlQWbC6cTj3iZK/uaGd7aLWFF paW49JxEhIjKp/ITRsZbNvW2cM2VbhoExgt8pPTT8LplxYdABxCUCxtvdnH1gULsnf RPWmjq8I2v+HI5osEvgcFOFvEYWAbGR1Uh7HFMtY= X-Authentication-Warning: sendmail: Host 92.40.4.124.threembb.co.uk [92.40.4.124] claimed to be fleabag.domlan.talk2dom.com Message-ID: <53D35794.4030305@talk2dom.com> Date: Sat, 26 Jul 2014 08:24:04 +0100 From: Dominic Froud User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: Using lagg References: <371D9ED786FD4379859A0993E8D12F15@multiplay.co.uk> <20140725222824.GN1065@hub.FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2014 07:24:09 -0000 On 25/07/2014 23:32, Sridhar Iyer wrote: > I was looking at sys/net/if_lagg.c, and wanted to know the usage of > functions such as lagg_ioctl(), lagg_input() etc. > > Regards, > > Sridhar > Those functions are part of the implementation of the lagg driver, internal to the kernel. They generally mirror similarly-named functions for all network drivers. xxx_ioctl() is for processing ioctl() calls from userland xxx_input() is for processing packets that arrive at the interface xxx_start() is for processing packets that are outbound from the interface xxx_create() for creating a new lagg interface xxx_attach() for attaching a laggport to a lagg interface and so on... If you want to programmatically attach, configure, modify, destroy lagg interfaces then you have choices like: shell scripts C code that performs the desired functions in the same way as ifconfig (userland) I can't see any immediate reason why you'd call functions like lagg_input() directly and you would have to be kernel-side to do so. What are you trying to achieve? Hope this helps! Dominic