From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sven@narfation.org>
From: Sven Eckelmann <sven@narfation.org>
Date: Fri, 12 Oct 2018 08:05:55 +0200
Message-ID: <6363727.6cOmail6FH@bentobox>
In-Reply-To: <CAEmTpZG2E2+4taAqrRpr0Yq_2HNte16wB2_gD87ZuN8aRnAOag@mail.gmail.com>
References: <CAEmTpZG2E2+4taAqrRpr0Yq_2HNte16wB2_gD87ZuN8aRnAOag@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart3566133.JIrdfNIaUc";
 micalg="pgp-sha512"; protocol="application/pgp-signature"
Subject: Re: [B.A.T.M.A.N.] BLA and gateway mode
List-Id: The list for a Better Approach To Mobile Ad-hoc Networking
 <b.a.t.m.a.n.lists.open-mesh.org>
List-Unsubscribe: <https://lists.open-mesh.org/mm/options/b.a.t.m.a.n>,
 <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=unsubscribe>
List-Archive: <http://lists.open-mesh.org/pipermail/b.a.t.m.a.n/>
List-Post: <mailto:b.a.t.m.a.n@lists.open-mesh.org>
List-Help: <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=help>
List-Subscribe: <https://lists.open-mesh.org/mm/listinfo/b.a.t.m.a.n>,
 <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=subscribe>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: =?utf-8?B?0JzQsNGA0Log0JrQvtGA0LXQvdCx0LXRgNCz?= <socketpair@gmail.com>

--nextPart3566133.JIrdfNIaUc
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"

On Freitag, 12. Oktober 2018 10:55:02 CEST =D0=9C=D0=B0=D1=80=D0=BA =D0=9A=
=D0=BE=D1=80=D0=B5=D0=BD=D0=B1=D0=B5=D1=80=D0=B3 wrote:
> Hello, guys.
>=20
> Does anybody know if BLA is somehow connected with gateway mode ?

No it isn't connected.

> In
> short, I'm unsure if gateway mode algorythms influence only DHCP
> traffic. It is not strictly said. Documentation about BLA II use term
> "gateway". As afr as I understand, there maybe case when BLA gateway
> is one node, and DHCP gateway is another one.

Correct

> So, the question: does
> GW functionality influence BLA algorythms ?

No

Kind regards,
	Sven
--nextPart3566133.JIrdfNIaUc
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEF10rh2Elc9zjMuACXYcKB8Eme0YFAlvAOcMACgkQXYcKB8Em
e0ZgWA//e++3BpvuqZB98KNiKMkIOO3sLeNr+NicB2KRK9Z9lRzUzjkkdl0goedy
HO/WblTEc8dP+/+lsPdJ86oNZJ2E8msMi4C/b7EyTyyYaNd2ievN4WpJR6jOaIGe
t2bt76Ee4aB6voktp6yjilrMRLyvpgMCsETq2Pt81PvWBljIxIxTUB1QEJN7WKQH
LigdVTQPa2ldkLCEbEF3qwp5gbvQw6qKPeA9CCMj9buHnl0Xh1IOcwHIeADPIkUv
zNcDwpNEV+iJXU2LOimmmI6vq/kv1yQFiLS2uWo+DD7tXMc5OAoGy3nHQyKk76Zm
88buaSP92gt+yeEvHNCdCIwJnHlSj7ZZbYxlL1lQEODhbck6SGJwL2lItoo+toba
aWYzdvwTi2wwM11lMmUfA6BD4DM14s6CUVGVnnmADcPeNiWVxjnU0KG1WJxHityG
SgnqZiQyBPRS7WaR3JqXa9Vqgqic1mcdjz4Wzsd/PcMM7rSJPft4FGH9OVZMkDQe
qsXHGyIqZNF90T9e1Oe7LDXnE54F991CqM2dTk8ZQouKXEa8kCsdRDM3frjZq3A0
W3XULFPt70EmgfbR4VTy+p99DYzuNQfVotaaVaQGO8eR01pbe0Ot+fNy7GSZG38m
ovPG5z4IoMldHlSnbAmn8rE7Bz/A7wOiwAWHC6DaOO+N1h2Svbg=
=ojiX
-----END PGP SIGNATURE-----

--nextPart3566133.JIrdfNIaUc--