iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAQMAAABtzGvEAAAABlBMVEX///8AAABVwtN+AAAAeklEQVQY04XQzQ2EIBAF4IdMDIc5UAIlUIKlWMr0ZiMm28jOj+6iMXEOfBBmXgJAVLGlBkU3wcZ9I3Q7EdrAveowx6hZ0q6QJDsRnHlJwr+W4CHF7vLqTEenXABeUnSssbP8SdwdjTHEwcFDtQGKFuWjH8Lna8vAmfEF3NMPdAOsBscAAAAASUVORK5CYII= Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit
Hi, I recently ran into a strange issue with netifd and was wondering if anyone else had see anything like it. I had a non-bridge interface on a router with with local-only ipv6 (that is no external ipv6, only the ipv6 from ula from the router), and noticed that dhcpv6 wasn't working. Eventually I noticed that ifstatus lanx reported and ipv6 of <hex:hex:hex>: (note the *single* colon) while bridge interfaces were reporting <hex:hex:hex>::. When I changed the interface to bridge it report <hex:hex:hex>:: and dhcpv6 addresses got served on that address. Methinks there may be an issue the prefix associated with non-bridge interfaces, but I don't know how to dig deeper on that. Not enough ipv6-fu for one thing. Also this is from a rather old version of netifd (from trunk) so it may be fixed already; opkg reports: 2016-03-04-da687c2689f7ff2af1dccc9a428806dd15c3d554 Once I finally get that router updated to newer trunk I'll report if the issues persists. Regards, Daniel _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
