From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Simon Wunderlich Date: Wed, 20 Jan 2016 16:48:40 +0100 Message-ID: <1795643.GVL5gPCguq@prime> In-Reply-To: <569FA7D1.9070604@unstable.cc> References: <1453296735-8319-1-git-send-email-sw@simonwunderlich.de> <569FA717.5090108@unstable.cc> <569FA7D1.9070604@unstable.cc> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3006348.ebrW9O7xXe"; micalg="pgp-sha1"; protocol="application/pgp-signature" Subject: Re: [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: move and restructure batadv_v_ogm_forward List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: b.a.t.m.a.n@lists.open-mesh.org Cc: Antonio Quartulli --nextPart3006348.ebrW9O7xXe Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="ISO-8859-1" On Wednesday 20 January 2016 23:29:21 Antonio Quartulli wrote: > On 20/01/16 23:26, Antonio Quartulli wrote: > > On 20/01/16 23:18, Simon Wunderlich wrote: > >>> this is changing the behaviour. > >>> here now we get a router which potentially was elected during the > >>> previous update_route() call while processing this very OGM. We are > >>> still discussing if we want to do this or not, but this patch should be > >>> just a style change, while this is not. > >> > >> No, this is already in the code which is merged into master - we already > >> acquire the updated router (see bat_v_ogm.c:547, function > >> batadv_v_ogm_route_update()). > > > > uhuhuh?! Actually you are right! > > This means we currently send one OGM every time we make an election, > > thus we might send multiple OGMs with the sequence numnber, despite this > > is still under debate. > > > > As far as I remember did not want to follow this approach at the moment? > > Am I missing something? > > I was missing this: > > + /* don't forward the same seqno twice on one interface */ > + if (orig_ifinfo->last_seqno_forwarded == ntohl(ogm2->seqno)) > + goto out; > + > > thanks Marek for pointing this out for me :) > > it's all good then! Ok cool! I guess we just need a conclusion where we put the conditions, then. :) Cheers, Simon --nextPart3006348.ebrW9O7xXe Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEABECAAYFAlafrFgACgkQrzg/fFk7axb+LwCfYY7qj4h4GszfwHr1Y1ORaoKZ TBMAoLI+3cpUYSAhB45uh/bToPzd+XAz =cA7Y -----END PGP SIGNATURE----- --nextPart3006348.ebrW9O7xXe--