From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.tohojo.dk (mail2.tohojo.dk [77.235.48.147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id C44CB21F2DE for ; Tue, 25 Nov 2014 23:40:25 -0800 (PST) X-Virus-Scanned: amavisd-new at mail2.tohojo.dk Sender: toke@toke.dk DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=toke.dk; s=201310; t=1416987243; bh=gJcLw0yHL6ppElTCrl22pQF0nOh/IhU0xKeWsMsGbD4=; h=In-Reply-To:References:Subject:From:Date:To; b=l779SDFP/R2PxjUUoEn3tvs9g5bpW/4qHH0nCsmG8CDp93Fv8On2qzrVZy1sMQGYM L/+RDfE0KTlUFMBIG/ja+kItYDv3D0Bva3S88Td7iSRZOBeZiitH4EG4JZQ+TJj6Qz xk7ktK6DSBWe0/zD1ejDltjmUxVz99wekuQ1QQ5s= In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 From: =?ISO-8859-1?Q?Toke_H=F8iland-J=F8rgensen?= Date: Wed, 26 Nov 2014 08:40:14 +0100 To: Dave Taht , "cerowrt-devel@lists.bufferbloat.net" , "babel-users@lists.alioth.debian.org" Message-ID: Content-Transfer-Encoding: quoted-printable Subject: Re: [Cerowrt-devel] ipv6 confusion with source specific gateways. 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: Wed, 26 Nov 2014 07:40:54 -0000 >default from :: via fe80::201:5cff:ee62:b646 dev ge00 proto static=20 >metric 1024 ># should I even have a default route at all? The source on this is actually ::/128 so it's not a default route in the = sense that it will forward arbitrary traffic through it. It is needed for= IPv6 packets that originate on the host but where the application doesn'= t specify an address to bind to. To see that, try removing it and then pi= ng6 something you don't have a specific route to... >Now, where my brain crashes: shouldn't 2601:c:ce00:9d1::/64 actually >be something like > >2601:c:ce00:9d01::/64 not, 2601:c:ce00:9d1::/64? > >(see the 01?)? 2601:c:ce00:9d01 is 2601:000c:ce00:9d01 2601:c:ce00:9d1 is 2601:000c:ce00:09d1 So no? :) -Toke