From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: From: "Lick A Prize" Date: Thu, 17 Sep 2009 12:01:29 +1000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0108_01CA378E.9758E6B0" Subject: [B.A.T.M.A.N.] IP from MAC 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: b.a.t.m.a.n@lists.open-mesh.net This is a multi-part message in MIME format. ------=_NextPart_000_0108_01CA378E.9758E6B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In the ROBIN address allocation described here = http://robin-mesh.wik.is/Documentation/Router_Configuring/Advanced_Config= uration/Robin_IP_Space I'm curious how collisions are avoided. If you generate IP 5.dd:ee:ff from aa:bb:cc:dd:ee:ff won't you get a = collision if you other devices with MACs ending in dd:ee:ff like = aa:aa:cc:dd:ee:ff, aa:aa:aa:dd:ee:ff, and so on. ------=_NextPart_000_0108_01CA378E.9758E6B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
In the ROBIN address allocation = described here http://robin-mesh.wik.is/Documentation/Ro= uter_Configuring/Advanced_Configuration/Robin_IP_Space=20 I'm curious how collisions are avoided.
 
If you generate IP 5.dd:ee:ff from=20 aa:bb:cc:dd:ee:ff won't you get a collision if you other devices with = MACs=20 ending in dd:ee:ff like aa:aa:cc:dd:ee:ff, aa:aa:aa:dd:ee:ff, and so=20 on.
------=_NextPart_000_0108_01CA378E.9758E6B0--