[Commotion-discuss] [Commotion-dev] Commotion R1 Changes

[Dan Staples]

We actually hadn't considered that since the access point handover is a
pretty large project for down the line. It was more for the sake of
simplicity, IIRC.

Handover aside, I also don't think retaining a client IP address would
be possible without some restructuring, since the 10.0.0.0/8 client
subnet on each router is chosen to be unique (in order to avoid
collision), i.e. the router assigns client IP addresses on the
10.a.b.0/24 range, where a and b correspond to the last two bytes of the
router's MAC address.

But it's still worth considering. Do you think retaining client IP
addresses would provide some benefits, as opposed to just getting a new
IP address when switching APs?

Dan

On 01/16/2014 10:20 AM, Ben West wrote:
> All of the addressing changes look like great ideas.
> 
> Question: is the decision to address all clients within the address
> space 10.0.0.0/8 <http://10.0.0.0/8> to, among other things, help make
> client roaming between nodes easier?  I.e. implying that clients would
> be assigned the same IP regardless of which node they associate with?
> 
> I noticed this item filed in the feature queue just now:
> https://github.com/opentechinstitute/commotion-router/issues/87
> 
> 
> On Fri, Jan 10, 2014 at 4:52 PM, Dan Staples
> <danstaples at opentechinstitute.org
> <mailto:danstaples at opentechinstitute.org>> wrote:
> 
>     Developers and network maintainers might want to check out our blog post
>     on significant backwards-imcompatible changes in the R1 release:
>     https://commotionwireless.net/blog/commotion-r1-breaking-changes
> 
>     In summary:
>     * Mesh IP addresses are now self-assigned in the 100.64.0.0/10
>     <http://100.64.0.0/10> range and
>     all client subnets are bridged and assigned addresses in the
>     10.0.0.0/8 <http://10.0.0.0/8>
>     range
>     * default adhoc SSID and channel were removed
>     * adhoc BSSID is now deterministically generated based on hash of SSID
>     and channel
> 
>     The blog post explains the details and reasoning behind these changes,
>     for those that are interested, and also includes info on upgrading
>     pre-R1 Commotion networks.
> 
>     You can also find R1 release notes here:
>     https://commotionwireless.net/blog/commotion-router-v1-release-notes
> 
>     cheers,
>     Dan
> 
>     --
>     Dan Staples
> 
>     Open Technology Institute
>     https://commotionwireless.net
>     OpenPGP key: http://disman.tl/pgp.asc
>     Fingerprint: 2480 095D 4B16 436F 35AB 7305 F670 74ED BD86 43A9
>     _______________________________________________
>     Commotion-dev mailing list
>     Commotion-dev at lists.chambana.net
>     <mailto:Commotion-dev at lists.chambana.net>
>     https://lists.chambana.net/mailman/listinfo/commotion-dev
> 
> 
> 
> 
> -- 
> Ben West
> http://gowasabi.net
> ben at gowasabi.net <mailto:ben at gowasabi.net>
> 314-246-9434

-- 
Dan Staples

Open Technology Institute
https://commotionwireless.net
OpenPGP key: http://disman.tl/pgp.asc
Fingerprint: 2480 095D 4B16 436F 35AB 7305 F670 74ED BD86 43A9