From: Radek =?ISO-8859-1?Q?Vok=E1l?= Date: Wed, 26 Oct 2005 08:51:48 +0000 Subject: [LARTC] Bug in ip -6? Message-Id: <1130316708.3197.10.camel@localhost.localdomain> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============1444333781==" List-Id: To: lartc@vger.kernel.org --===============1444333781== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-io87SJ75KDsnGWUdK8KP" --=-io87SJ75KDsnGWUdK8KP Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, this appeared on Red Hat bugzilla and I'm not sure if customer presumption is correct `ip -6 route add 10::a120/124 via 10::a111` returns RTNETLINK answers : invalid argument His expected result is that route table to subnet 10::a120/124 should be added I know RFC3587 described prefix 001b is the unicast global address range assigned by IANA, and all other unicast address rage is 'unassigned'. But 'unassigned' does not mean illegal. It's only administrative purpose. Implementation should not get such restriction. Is he correct? Should this be fixed? --=20 Radek Vok=C3=A1l --=-io87SJ75KDsnGWUdK8KP Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBDX0OkpPtjDwJDWJMRAjtRAKCZqgvNl6K6BJvDLZBz1HHd8BCPiQCgnD96 LA/LTqd/FBBSF3sG0HZ8Ub8= =Bh+h -----END PGP SIGNATURE----- --=-io87SJ75KDsnGWUdK8KP-- --===============1444333781== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc --===============1444333781==--