From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) by huchra.bufferbloat.net (Postfix) with ESMTP id 5399D21F151 for ; Thu, 16 May 2013 12:23:03 -0700 (PDT) Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 68C602016E; Thu, 16 May 2013 15:34:49 -0400 (EDT) Received: by sandelman.ca (Postfix, from userid 179) id 48A6A63A7E; Thu, 16 May 2013 15:21:53 -0400 (EDT) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 36FBD63A7C; Thu, 16 May 2013 15:21:53 -0400 (EDT) From: Michael Richardson To: Steven Barth In-Reply-To: <518679F3.8050509@openwrt.org> References: <29781.1367350165@sandelman.ca> <26206.1367413101@sandelman.ca> <518679F3.8050509@openwrt.org> X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22) X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Sender: mcr@sandelman.ca Cc: cerowrt-devel Subject: Re: [Cerowrt-devel] shaggy dog story on 3.8.8-4 experiences X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 May 2013 19:23:03 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable >>>>> "Steven" =3D=3D Steven Barth writes: Steven> I was on holiday until yesterday so my reply is a bit late. Thank you for the reply! >> which means that any subnet that isn't allocated anywhere does not >> result in a routing loop. It also causes the 6relayd to assign pref= ixes >> to each interface. >>=20 >> I will see if I can hack on 6relayd, because I really like this. Steven> This is actually done by netifd, not 6relayd. 6relayd is the Steven> RA/DHCPv6-server=20 Steven> used in OpenWrt trunk (CeroWrt uses dnsmasq here I think) and p= rovides most Steven> of the homenet functionality (RFC 6204 should be pretty much co= vered by Steven> OpenWrt with very few exceptions - I think only one) okay, I see. I would have thought that since the prefix came down via DHCPv6, that this was being done there too. I will read through netifd. >> >> At least one prefix is behind another router, so this router can = not >> >> see that prefix is already in use. Suggestion: start at highest >> >> number available and work downwards. Dave> Two interior prefix allocation methods have been described by the Dave> homenet and hipnet rfcs. openwrt follows neither at present. :-) >> sure, that's not the point. The point is that the set of "prefixes = in >> use" is not limited to just those on local interfaces, but also ones >> that might have a static route elsewhere. Yes, I agree that routing >> protocols are important and useful... that's why I have 4x 3800 now = for >> play and testing :-) >>=20 >> The incidence of conflict would be less if the auto-assigned numbers >> started from highest number. At least for me, it would. Steven> That's imo not a good idea because it doesn't really solve the = issue. I understand... I wasn't suggesting it would solve the problem, just make it less of a toe stumbing event. Steven> I could modify the assignment logic in netifd to scan through a= ll ip6addrs Steven> configured before distributing any prefixes and exclude ip6addr= assigned Steven> prefix parts from being reassigned again. That's really what we need. Steven> Regarding the other cases: It is possible to set ip6assign to s= omething <64 Steven> so that a bigger prefix is assigned to a downstream-interface. = With 6relayd Steven> as DHCPv6-server this automatically makes anything but the firs= t /64 Steven> available on the interface to downstream routers via Steven> DHCPv6-PD (the first /64=20 Steven> is announced using RAs on the interface). wow, that's really cool. I will actually use this then so that my main router can then play ISP for my test router... Steven> The technically better solution would be a mechanism where prog= rams could Steven> request a prefix via some RPC-mechanism from netifd. However Steven> this would need=20 Steven> synchronization and callback-mechanism to inform the routing da= emon when a Steven> prefix is assigned / deassigned etc. dare I suggest... dbus? I know that network manager already sends out dbus messages about new prefixes configured, and things like pidgin listen and reconnect when they see a new prefix. "everyone is doing it" (even the Automotive people) =2D-=20 ] Never tell me the odds! | ipv6 mesh network= s [=20 ] Michael Richardson, Sandelman Software Works | network architect= [=20 ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails = [=20 =09 --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQCVAwUAUZUx0YqHRg3pndX9AQJ0yAQAtAS2cezzGIh0+7Yg/u8hk2y4c4bC719F sdDiOqlkmqEm5nV2p7sVXza5tr5Rz2IROv8NYKZ0IoUZoVGVWeTOeQomXIf1G7Mv p/6SE2hN0d/cQ1rlsCI5hXq8x12KmwSlK2CYPh23WupEAV/vnwA5PNv46Nl/5R4w znpq9jU3Aqg= =Y4k3 -----END PGP SIGNATURE----- --=-=-=--