From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Thu, 5 Apr 2012 23:08:23 +0300 References: <201203222250.31309.lindner_marek@yahoo.de> <1332453075-27999-2-git-send-email-lindner_marek@yahoo.de> <20120323212233.GG5662@lunn.ch> In-Reply-To: <20120323212233.GG5662@lunn.ch> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201204052308.23891.lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] [RFC 2/5] batman-adv: ELP - creating neighbor structures, updating LQs Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking On Friday, March 23, 2012 23:22:33 Andrew Lunn wrote: > I've not looked at the code, but i assume this can happen because > there is not a per algorithm receive handler? Maybe it makes sense to > have a receive handler in algo structure, which can handle per > algorithm receive functions? The common PDUs can be handled first and > then a call into the algo receive function made to dispatch algo > specific PDUs. Each algorithm registers its own packet types which end up in the protocol specific receive function. Nevertheless, we might receive a B.A.T.M.A.N. V packet on an interface not running B.A.T.M.A.N. V. Regards, Marek