From: Dave Taht <dave.taht@gmail.com>
To: Vincent Frentzel <zcecc22@c3r.es>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] IPV6 success on 3.10.28-14 with 6to4 tunnel and 6relayd
Date: Sun, 23 Feb 2014 22:15:14 -0500 [thread overview]
Message-ID: <CAA93jw7RG4o5Pi9YsoBMNKN8GVmUyGo3EbNz=ruccOHFCZ2Ocg@mail.gmail.com> (raw)
In-Reply-To: <CACCCjEUtkTw+Od7xgnJBCuUyQkd9DPCnSyiAYduEYWMvBtiyUg@mail.gmail.com>
until very recently I was using the dnsmasq version of the RA stuff,
(basically uncommenting
everything in /etc/dnsmasq.conf )
I was under the impression that what I'd had switched to worked, but didn't
try this scenario. (it seems to work on the default gw box, but not internally)
I tend to pretty much run babel everywhere, too, which doesn't help...
Anyway, on the interior gateway I have going...
I statically assign something available from my /60 to the se00
interface, and I no longer get a message from
that interface saying this:
Mon Feb 24 03:07:03 2014 daemon.warn odhcpd[1318]: A default route is
present but there is no public prefix on gw00 thus we don't announce a
default route!
Mon Feb 24 03:07:03 2014 daemon.warn odhcpd[1318]: A default route is
present but there is no public prefix on sw00 thus we don't announce a
default route!
Mon Feb 24 03:07:03 2014 daemon.warn odhcpd[1318]: A default route is
present but there is no public prefix on gw10 thus we don't announce a
default route!
Mon Feb 24 03:07:03 2014 daemon.warn odhcpd[1318]: A default route is
present but there is no public prefix on sw10 thus we don't announce a
default route!
(so I assume it's trying to announce a default route to the se00
interface, or at least thinks it is)
I am seeing the /60 inserted into the local default table as well as a
generic route inserted by ras...
default from :: via fe80::8e:f2ff:fefa:a153 dev ge00 proto static metric 1024
default from 2601:9:6680:530::/60 via fe80::8e:f2ff:fefa:a153 dev ge00
proto babel metric 1024
so I:
killall -1 odhcpd # this forces a RA
But in doing that, I am not seeing a default route announced via RA
via radvdump. Sigh.
prefix 2601:X:Y:535::/64
{
AdvValidLifetime 7200;
AdvPreferredLifetime 1800;
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
}; # End of prefix definition
RDNSS 2601:X:Y:535::1
{
AdvRDNSSLifetime 1800;
}; # End of RDNSS definition
DNSSL desk.armory.com
{
AdvDNSSLLifetime 1200;
}; # End of DNSSL definition
/etc/config/dhcp has this in it, which sort of matches your 6relayd config
config dhcp 'se00'
option interface 'se00'
option start '2'
option limit '26'
list dhcp_option '42,0.0.0.0'
list dhcp_option '44,0.0.0.0'
list dhcp_option '45,0.0.0.0'
list dhcp_option '46,8'
option leasetime '24h'
option domain 'desk.armory.com'
option ra 'server'
option dhcpv6 'server'
On Sun, Feb 23, 2014 at 9:35 PM, Vincent Frentzel <zcecc22@c3r.es> wrote:
>> > Hi everyone,
>> >
>> > After struggling a while with odhcpd and route propagation I wanted to
>> > report that I got ipv6 working with the following config for 6relayd.
>>
>> I am under the impression that 6relayd is now obsolete and that these
>> are controlled in the /etc/config/dhcp file.
>
>
> That is correct. However, when using odhcpd I could nt get IPV6 routing over
> different segments (ie pings from SW10 to SE00 gave network unreachable).
> In the end 6relayd worked althoug Im not sure why.
>
> Im curious to see if anyone has encountered the same issue.
>
>
> On Sun, Feb 23, 2014 at 5:07 PM, Dave Taht <dave.taht@bufferbloat.net>
> wrote:
>>
>> On Fri, Feb 21, 2014 at 12:15:13AM +0100, Vincent Frentzel wrote:
>> > Hi everyone,
>> >
>> > After struggling a while with odhcpd and route propagation I wanted to
>> > report that I got ipv6 working with the following config for 6relayd.
>>
>> I am under the impression that 6relayd is now obsolete and that these
>> are controlled in the /etc/config/dhcp file.
>>
>> >
>> > config server se00
>> > list network se00
>> > option rd server
>> > option dhcpv6 server
>> > option management_level 1
>> >
>> > config server sw00
>> > list network sw00
>> > option rd server
>> > option dhcpv6 server
>> > option management_level 1
>> >
>> > config server sw10
>> > list network sw10
>> > option rd server
>> > option dhcpv6 server
>> > option management_level 1
>> >
>> >
>> > Hope this can be of use to someone or contribute to the next release :)
>> >
>> >
>> > BR,
>> >
>> > Vincent
>>
>> > _______________________________________________
>> > Cerowrt-devel mailing list
>> > Cerowrt-devel@lists.bufferbloat.net
>> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2014-02-24 3:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 23:15 Vincent Frentzel
2014-02-23 17:07 ` Dave Taht
2014-02-24 2:35 ` Vincent Frentzel
2014-02-24 3:15 ` Dave Taht [this message]
[not found] ` <631f38e0-0042-4f4d-a8df-4975dc497ab7@email.android.com>
2014-02-24 15:27 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7RG4o5Pi9YsoBMNKN8GVmUyGo3EbNz=ruccOHFCZ2Ocg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=zcecc22@c3r.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox